Software Vault: The Gold Collection

home *** CD-ROM | disk | FTP | other *** search

/ Software Vault: The Gold Collection / Software Vault - The Gold Collection (American Databankers) (1993).ISO / cdr28 / ll210exe.zip / LAN-DOC.2 < prev next >

Wrap

Text File | 1993-05-11 | 204KB | 5,153 lines

Appendix 2 Page 80 Configuration file. 18.19.3 The PacketCluster Call This option allows you to change the default PacketCluster Call without connecting to it. 18.20 Change Directories This sub-menu allows you to change the Directories used by LAN- LINK, as described in the following paragraph. 18.20.1 Capture-to-disk files Directory This is the drive and directory that LAN-LINK will put the *.RUN capture-to-disk files. Note: the last "\" MUST be present if you are using a different sub-directory. 18.20.2 QBM Download Directory This is the directory the :QBM: command will search to find a file to be downloaded. The default directory for the files is \LAN-LINK\FILES\. Note: the last "\" MUST be present. 18.21 Enter Common Calls Each time you call another station, LAN-LINK remembers it (up to the last 16). When you update the SYS file, those calls will be saved to disk. You can use this option to add calls, delete calls or edit calls in the list. Use the "Delete" key to delete a call. 18.22 Change File Names This sub-menu allows you to change the default file names used by LAN-LINK, as described in the following paragraphs. 18.22.1 VHF Logbook File (VHF.DBF) This is the name of the file to be used as your VHF Packet logbook. 18.22.2 HF Logbook File (HF.DBF) This is the name of the file to be used as your HF logbook. It is used for all HF modes, including HF packet. 18.22.3 Path Directory File (LAN-LINK.DIR) This is the name of the file used as your call directory. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 81 18.22.4 Brag Tape (LAN-LINK.TXT) This is the name of the file used as your brag tape. 18.22.5 QBU Upload File Name (QBU-TX.BAT) This is the name of the batch file used to initiate a QBU. 18.22.6 QBU Download File Name (QBU-RX.BAT) This is the name of the batch file used when a :QBU: command is received from a remote station. 18.23 Change LAN-LINK Parameters This sub-menu allows you to change the LAN-LINK Parameters, as described in the following paragraphs. 18.23.1 Change CQ Text This feature allows you to change the contents of the CQ text message string. This is the message string that is transmitted along with the CQ call. Think of this message as a CQTEXT line. 18.23.2 Set CQ Delay Time (Seconds) This option allows you to change the time (seconds) that the LAN- LINK waits for a response after a CQ call until the following one is transmitted. The default value (in minutes and seconds) is loaded from the LAN-LINK.SYS file. 18.23.3 Set CQ Delay Time (Minutes) This option allows you to change the time (minutes) that the LAN- LINK waits for a response after a CQ call until the following one is transmitted. The default value (in minutes and seconds) is loaded from the LAN-LINK.SYS file. 18.23.4 Set Connect Time Timeout (Minutes) This option allows you to change the time (minutes) that the LAN- LINK waits for a response in a packet connect before issuing a Disconnect command. The default value is loaded from the LAN- LINK.SYS file. 18.23.5 Set Number of Lines in a Non-Contest CQ Call This option allows you to change the number of lines in a non- contest CQ call from the default value of 3 to any number you wish. The default value is loaded from the LAN-LINK.SYS file. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 82 18.23.6 Keyboard Beep Character Count When your typing at the keyboard gets to a point where you may overrun the normal line length, LAN-LINK issues a beep to remind you to touch the "Enter" key. This option allows you to change the number of characters you can type in a line before the beep sounds. Note the beep will not sound if the sound flag is inhibited. 18.23.7 Word Wrap Mode This option allows you to change the word wrap mode. It is really more of a "force carriage return" parameter, rather than "word wrap". There are four options as follows: 18.23.7.1 Off: Word wrap is off. 18.23.7.2 AutoCR: LAN-LINK will insert an "Enter" character for you into the outgoing text when you enter the first space character after the beep has sounded. 18.23.7.3 Word: LAN-LINK will hold all entered text until you either type a space character or touch the "Enter" key. At that time LAN-LINK will send the word to the TNC. 18.23.7.4 Line: LAN-LINK will hold all entered text until you either touch the "Enter" key or the beep sounds. At that time LAN-LINK will send the word to the TNC. Set this parameter value as follows, 0 = OFF, 1 = AutoCR, 2 = Word, 3 = Line. 18.23.8 Set Shut Down Mode (QRT Flag) This option allows you to customize the shut down and start up sequences of the TNC as described in the following sections. If the Shut down mode is not set to 1, you also have the option to customize the packet terminal mode. 18.23.8.1 State 0: On shut down, turns the TNC into a VHF Digi- peater and turns CONOK OFF (CFROM NONE for the PK-232). In this condition the TNC will reject connect requests. On start up turns CONOK or CFROM on. 18.23.8.2 State 1: Does not send any commands to the TNC on shut down or start up. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 83 18.23.8.3 State 2: On shut down, sends CMSG ON to the TNC. On start up, sends CMSG OFF to the TNC. 18.23.8.4 State 3: On shut down, turns on the mailbox in the TNC. On start up turns off the mailbox. 18.23.8.5 State 4: On shut down, turns on the mailbox in the TNC and puts the TNC into the SOLO Mode so that the internal buffer in the TNC does not fill with on-the-air traffic. On start up turns off the mailbox. 18.23.9 Set Default Users This option allows you to set the maximum number of multiple users that can be connected to your TNC at the same time, and to configure the default start up mode of the program. If this parameter is set to 1, LAN-LINK will configure itself to the single user mode, and set the maximum number of users to 9. If this parameter is set to any number other that 1, LAN-LINK will assume that value to be the maximum number of allowed connects, and configure itself in the Multiple user Mode (equivalent to the TNC Menu Option 0). 18.23.10 Set UTC Offset This parameter contains the difference in hours between Universal Co-ordinated Time (UTC) and your local time. For example, if you are located on the east coast of the U.S.A., and it is winter, you are in the Eastern Standard Time (EST) Zone, which is 5 hours behind UTC. In this case, the value of the UTC Offset parameter is 5. Don't forget to change this parameter when the clocks are adjusted each spring and autumn. 18.23.11 VHF Packet Length This option allows you to change the default VHF packet length. The TNC has a maximum permissible value of 255. Set the parameter to 127 or 255. 18.23.12 HF Packet Length This option allows you to change the default HF packet length. The default value of about 30 seems to be optimal. 18.23.13 Beacon Time This option allows you to change the default beacon time. The KAM requires a value in minutes, all other TNCs in tens of seconds. Use good operating practice and don't beacon too often. Every 30 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 84 minutes on a well used channel is more than enough. 18.23.14 Custom Prompt before "Over" This option allows you to add a word or two (up to 20 characters) before the ">" in packet or the "+?" in AMTOR. If you are working an AMTOR APLINK PBBS, clear this feature by changing it to a space character. 18.23.15 Packet Cluster DX Alert Mode This parameter determines the action LAN-LINK takes when you are connected to a PacketCluster, and a DX Alert message shows up. The states are 0, 1, 2, or 3. If it is 0, LAN-LINK takes no action at all. In all other states, LAN-LINK splits the prefix from the DX callsign, searches the HF logbook for the prefix and posts a message in the status window (in the Alert Call color) as follows: Prefix, Logbook Status, DX callsign. The logbook status shows up as 'Q' for QSL'd, 'W' for worked and '?' for not in log. You can configure LAN-LINK to generate an audible alarm for each condition to save you monitoring the screen. If the Sound is inhibited, the audible alarm will also be inhibited. The visual display and audio alarms are controlled by this parameter as shown below. State QSL'd (Q) Worked (W) Not in Log (?) 0 No Action No Action No Action 1 Audio + Display Audio +Display Audio + Display 2 Display Audio + Display Audio + Display 3 Display Display Audio + Display You can customize the CW tone and speed, by changing the states of the "Packet Cluster DX Alert Tone CW Dit time" and "Packet Cluster DX Alert Tone CW Note" parameters in the LAN-LINK.SYS File. In this version of LAN-LINK, the prefix scan is simple minded, so set this parameter to 3 to get used to it, then set it to 1. 18.24 Change PC Communications Parameters This sub-menu allows you to change the Communications Parameters between the PC and the TNC, as described in the following paragraphs. 18.24.1 The Communications Port This is the default Communications port. The default value is 1. You may set it at any value between 1 and 4. If you only have one LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 85 serial port in your PC, set the parameter to "1" even if your card is configured as Com2. LAN-LINK will ALWAYS assume Com1 for a single card. If you use a different port instead of Com1, and plan to do binary transfers, don't forget to customize the QZ*.BAT files. The default Com3 and Com4 default PC port values are as follows. Port Address(Hex) Address (Decimal) IRQ Com3 3E8 1000 4 Com4 2E8 744 3 If you set the port number to 0, LAN-LINK will not accept or transmit any character to the serial port. All other features will work. 18.24.2 The Terminal Baud Rate This Parameter tells LAN-LINK what baud rate the TNC is set to. This is the baud rate on the RS-232 line between the TNC and the PC. Valid baud rates for LAN-LINK are 300, 1200, 2400, 4800, 9600 and 19,200. If you specify something else LAN-LINK will default to 1200. You may experience problems when using baud rates greater than 1200. It depends on the CPU clock rate, any TSR's in the PC, and the I/O card in the PC. LAN-LINK scans the incoming text constantly, something which requires time. My PK-232, when used with my XT Clone at 10MHz, does not like baud rates faster than 2400, and sometimes not even that. The PK-232 seems to drop the first character of some lines at 4800 baud. Use 1200 until you have tested, and are sure that a faster one will work. This program has been tested on a TNC2 and an MFJ1278 using a terminal baud rate of 9600 baud and worked correctly. It also works correctly with a KAM at 2400 Baud. If you use a different rate instead of 1200, and plan to do binary transfers, don't forget to customize the QZ*.BAT files. 18.24.3 TNC Data Bits You can set the number of data bits on the RS-232 line between the PC and TNC to 7 or 8. Use 7 with a TNC2 if you have problems with Greek characters. Set this value to either 7 or 8. 18.24.4 TNC Parity Use this parameter to set the Parity bit on the RS-232 line between the PC and TNC. Enter the letter corresponding to the LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 86 desired parity. N = None, O = Odd, E = Even, M = Mark, S = Space. 18.24.5 Number of TNC Stop Bits You can set the number of stop bits on the RS-232 line between the PC and the TNC to 1 or 2. Use 1 at all terminal (not packet) baud rates except 300. Set this value to 1 or 2. 18.25 Change Colors This option lets you change the default colors. A display of all of the combinations is shown on the left side of the screen. You will then be prompted to sequence through each window/message color that can be customized. Enter the number shown in the combination window followed by the "Enter" key to set a value. If you don't wish to make a change, just press the "Enter" Key. The following identifications are made to the color choices: 18.25.1 OutWindow Color This is the color of the text (typed at the keyboard) in the outgoing window. 18.25.2 StatusWindow Color This is the color of the Status Window. 18.25.3 PromptWindow Color This is the color of most of the menus. 18.25.4 LogWindow Color This is the color of the text in the log window. 18.25.5 InWindow Color This is the color of the text in the window showing the incoming characters. 18.25.6 ScrollBack Window Color This is the color of the text in the Scroll back window. 18.25.7 MHWindow Color This is the color of the text in the monitor heard calls (MH) window. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 87 18.25.8 Alarmwindow Color This is the color of the text in the Error and Alarm window. 18.25.9 BottomWindow Color This is the color of the text in the prompt line at the bottom of the screen. 18.25.10 Emphasis Color This is the color of the emphasized text in the Menu windows. 18.25.11 Prompt Color This is the color of the prompt text in the Menu windows. 18.25.12 Option Color This is the color of selected option text in the Menu windows. 18.25.13 Connected Text Color This is the color of the text in the incoming window when connected in the packet communications modes. 18.25.14 Computer Color This is the color of the computer generated text in the outgoing window when the Command Echo Flag option is enabled. 18.25.15 VHF Header Color This is the color of the VHF Header lines in the Incoming window when not connected. 18.25.16 HF Header Color This is the color of the HF Header lines in the Incoming window when not connected. 18.25.17 Alert Call Color This is the color of the packet header lines containing the Alert call in the Incoming window when not connected. It is also the color of the non-permanent Parameter Menu prompts. 18.25.18 Outgoing Text Color This is the color of the outgoing text echoed in the Incoming LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 88 window in the AMTOR Communications Mode. 18.25.19 Multi I/O Stream Color[1] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 1. 18.25.20 Multi I/O Stream Color[2] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 2. 18.25.21 Multi I/O Stream Color[3] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 3. 18.25.22 Multi I/O Stream Color[4] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 4. 18.25.23 Multi I/O Stream Color[5] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 5. 18.25.24 Multi I/O Stream Color[6] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 6. 18.25.25 Multi I/O Stream Color[7] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 7. 18.25.26 Multi I/O Stream Color[8] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 8. 18.25.27 Multi I/O Stream Color[9] This is the color of the text lines in the Incoming window in the Multiconnect Mode when connected to I/O stream 9. 18.25.28 Multi I/O Stream Color[10] This is the color of the text lines in the Incoming window in the LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 89 Multiconnect Mode when connected to I/O stream 10. When you change the colors, LAN-LINK does not overwrite all existing windows. If you want to be sure of seeing the changed colors, save the color changes using the Update option, and then exit from and reload LAN-LINK. 18.26 Change SAREX Parameters This sub-menu allows you to change the SAREX Ground Station parameters, as described in the following paragraphs. 18.26.1 SAREX CallSign This is the callsign of the SAREX station. 18.26.2 Change SAREX Capture to Disk File This option lets you change the name of the SAREX Capture- to- disk file. Don't change file names while "capture-to-disk" is in progress (when a flashing "[S]" in present in the status window), or the old one will stay open and may not close properly when LAN-LINK is terminated, resulting in data loss. 18.27 Update Configuration File Use this option to save the changes (permanently) in the configuration file (LAN-LINK.SYS). Activate it twice to see most of the changes. 18.28 Verify Changes This feature lets you display how LAN-LINK was configured by the LAN-LINK.SYS file. It also displays the state of any flags you have set/reset if they are not already shown in the Status window or Parameter Menu. 18.29 Change Scan Words In the ZAP PBBS feature you can ask the program to scan the lines read from the PBBS and if it sees any of the scan words in the line, it will queue a request for that bulletin by number. You can only set 16 such Scan words (should be enough) and request up to 255 messages/bulletins at a time. Use the "Delete" key to delete a word from the list. Words that show up in the PBBS prompt line cannot be used as scan words. For example, if your PBBS prompts you with LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 90 N4QQ PBBS> then "N4QQ" and "BBS" should not be used as Scan Words. Don't leave a blank line in the Scan Word section of the configuration file. 18.30 Turn Miscellaneous Flag ON/OFF The Miscellaneous Flag performs several different functions in the different Communications modes as follows. 18.30.1 All Modes:- Debug or state-sequence numbers Shows two debug or state-sequence numbers in left hand corner of the status window in the format N-M]. N is the BBS State and M is the Communications State. These are used to figure out what went wrong in the automatic sequences. If an automatic sequence fails to work, set the miscellaneous flag, and observe the state in which LAN-LINK seems to hang. It will be waiting for something, and you should get a clue as to what, from Table 18.30.1. BBS State (N) numbers are shown in Table 18.30.1-A and the Communications states are shown in Table 18.30.1-B. Table 18.30.1-A BBS States 1 Connected to BBS waiting for first '>' 2 Receiving incoming messages 3 Receiving list of new messages 4 Receiving your messages (in case missed some) 5 Custom command (i.e. KM) 6 LAN-LINK QTC Snatch in progess 7 Receiving Mail going to YOURCALL.OUT 8 :QDB: waiting for QRV/QNO 9 :QDB: sending file waiting for QSL/QNO 10 AUto UPload Opening BBS.BBS command file 11 AUto UPload sending one line command 12 AUto UPload sending subject line of message 13 AUto UPload sending message 14 AUto UPload waiting for last '>' before disconnecting 22 Recieiving file 25 Packet cluster connect waiting for first '>' 26 Packet cluster connect waiting for first '>' Table 18.30.1-B Communications States 0 Disconnected packet mode or normal non packet mode. 1 Connected in packet mode 2 Trying to connect in packet mode 3 Trying to disconnect in packet mode 4 Sending mail file in packet mode LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 91 5 ARQ called someone, or in QSO 6 Connected in autocq mode 7 Calling autocq in packet 8 Sending file in autocq 9 Waiting for reply in autocq packet 10 Autocq non packet sending CQ message 11 Autocq non packet waiting for reply 12 SELCAL waiting for ZCZC or YOURCALL 13 SELCAL waiting for NNNN 14 Autocq AMTOR sending bragtape 15 Autocq AMTOR receiving message 16 Autocq AMTOR requesting repeat of his_call 17 Autocq MFJ1278/KAM waiting for 73 to complete and sign off 21 QRU mode packet 22 Calling someone in pactor 25 AMTOR sending :QQQ: response 26 QRU mode packet 18.30.2 BAUDOT Mode:- Navy MARS Protocol Verify When the flag is set, and the BAUDOT Navy MARS option is enabled, the character string ":CR:" will be displayed in the outgoing window each time a carriage return character is received in the incoming window. Similarly, every time a line feed character is received, a ":LF:" will be displayed in the incoming window. You may use this feature to verify that another station is sending files using the correct protocol. If you do, make sure that you tell the PK-232 not to add a line feed to incoming carriage returns by setting the ALFD parameter to OFF in the Com- mand Mode. You will have to set "ALFD ON" again when you change to other communications modes, or all incoming lines will overwrite each other. 18.31 Change Band/Mode This option is used to set the band and radio mode without invoking the Log Menu. You can use it when changing bands on HF before logging a new QSO. The value is not remembered when you shut LAN-LINK down, unless you log the QSO. 18.32 Zap PBBS on Next Mail Beacon This parameter causes LAN-LINK to Zap your local PBBS next time it beacons with a list of calls for which it has Mail. 18.33 PBBS Zap, Don't Disconnect After Sequence This parameter stops LAN-LINK from issuing the automatic disconnect when the Zap sequence is over. You can set it during LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 92 the Zap sequence. Use it to stop the disconnect if the sequence gets out of sync with the messages, or if there is something interesting you wish to do to the PBBS. This parameter resets when the Zap sequence terminates. 19.0 Q Codes [NC/L] This option displays help information about the use of the Network Communications Language (NC/L) "Q" codes. 20.0 COMMUNICATIONS MODES This menu allows you to change the communications mode of the TNC. If your TNC hardware cannot support those modes, don't bother to try them. This is software not hardware, and in spite of what people tell you, software can't do everything. The commu- nications modes shown in Figure 20 are available. Type in the single letter to make your choice. While the KAM ports are set, and the MFJ-1278 ports are defaulted in LAN-LINK (1 = VHF, 2 = HF), don't forget that YOU HAVE to select the correct radio port on the PK-232. Figure 20 PK-232 Communications Mode Menu V VHF PACKET H HF PACKET A AMTOR (STANDBY) B BAUDOT (RTTY) C MORSE (CW) M AMTOR (MONITOR) P PACTOR (STANDBY) Q PACTOR (MONITOR) S ASCII (RTTY) N NAVTEX G SIGNAL 20.1 VHF PACKET This is the 1200 baud VHF Packet Mode. LAN-LINK will optimize the TNC link parameters for this mode. 20.2 HF PACKET This is the 300 baud HF Packet Mode. LAN-LINK will optimize the TNC link parameters for this Mode. 20.3 ASCII (RTTY) This is the ASCII RTTY Mode. LAN-LINK will configure the TNC parameters for this Mode at 110 baud. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 93 20.4 BAUDOT (RTTY) This is the BAUDOT RTTY Mode. LAN-LINK will configure the TNC parameters for this Mode at 45 baud. 20.5 MORSE (CW) This is the CW Mode. LAN-LINK will configure the TNC parameters for this Mode at the default CW speed (20 for the PK-232 and MFJ- 1278, 10 wpm for the KAM). In this Mode the ALT-D Key will disengage the receive speed lock inside the PK-232 to facilitate locking onto another signal and Function Key 8 (F8) will turn the transmitter off. LAN-LINK has a flag in the configuration file that lets you configure the XMITOK parameter in the TNC. This flag allows you to set XMITOK to "OFF" when you enter the CW communications mode, and turn it "ON" again when you exit from the CW communications mode. 20.6 AMTOR (STANDBY) When you select the AMTOR Standby Mode you are placed into the "Standby Receive" Mode. If you are in AMTOR Standby Mode, you will not be able to display signals of the Chirpcopy Mode (which means that you will not be able to display a QSO in progress). The Alt-D Key and Function Key 8 (F8) both toggle between the AMTOR STANDBY and MONITOR communications modes. 20.7 AMTOR (MONITOR) If you want to read the mail on an existing AMTOR QSO in progress, select the AMTOR (MONITOR) or Chirpcopy Mode. The Alt-D key and Function key 8 (F8) both toggle between the AMTOR STANDBY and MONITOR communications modes. 20.8 PACTOR (STANDBY) When you select the Pactor Standby Mode you are placed into the "Standby Receive" Mode. If you are in Pactor Standby Mode, you will not be able to display signals from a QSO in progress. The Alt-D Key and Function Key 8 (F8) both toggle between the Pactor STANDBY and MONITOR communications modes. 20.9 PACTOR (MONITOR) LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 94 If you want to read the mail on an existing Pactor QSO in progress, select the Pactor STANDBY or Chirpcopy Mode. The Alt-D key and Function key 8 (F8) both toggle between the Pactor MONITOR and STANDBY communications modes. 20.10 SIGNAL Use this option to select the PK-232 SIGNAL Mode. Read the PK-232 documentation carefully to understand how this mode works. Once the PK-232 has identified the digital signal it is tuned to, use the Communications Mode Select Menu a second time to select the relevant mode and then set the baud rates and shift to display the data if necessary. 20.11 NAVTEX Use this option to select the NAVTEX Mode. Read the TNC documentation carefully to understand how this Mode works. 21.0 TERMINAL MODE MENU This menu allows you to set the Terminal Configuration Mode. The Terminal Menu provides different choices depending on which communications mode you have selected. 21.1 Packet Terminal Menu The Packet Terminal Mode of operation will be shown in the Status window at the top of the screen. If you are reading the mail on a station, the callsign of that station will be shown next to the word "MAIL". If you are connected to someone, the call (and path) will be shown prefixed by the "*>" sequence. In the Packet Communications Mode, you are presented with the choices shown in Figure 21.1. Type in the single letter to make your choice. 21.1.1 Change Packet Baud Rate In the PACKET Mode you may change the RF baud rate between 300, 600, 1200 and 2400 baud. While LAN-LINK allows these baud rates, the TNC may not. 21.1.2 CQ/Beacons In this Mode, you will see CQ and BEACON packets on the channel. This Mode only works on the PK-232 and the KAM. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 95 Figure 21.1 Packet Terminal Menu B Change Packet Baud Rate C CQ/Beacons E Everything I Information L Turn MCON ON M Read the Mail O Turn Meta Beacon ON S Just My Station (Solo) T All Traffic 0 Multiple User Connects F Turn Conference ON 21.1.3 Everything You can set the TNC Mode to "Everything", i.e. show all packets on the LAN. 21.1.4 Read the Mail You can read the mail on a PBBS or other station and get bulletins without connecting to that station yourself. You use this Mode to do so. You will be prompted for the call whose packets you wish to monitor. Remember to enter the call of the station sending the packets, not the call of the one receiving them. This mode only works without showing the packet headers on the PK-232. On the other TNCs the headers will also be displayed. You can also use this command to monitor both sides (read the mail) on a QSO on a busy packet channel. You may want to turn the Digipeat Data Display Mode off when reading the mail. 21.1.5 Just My Station (Solo) In this Mode, you will only see messages addressed to you. You will only get messages from people who connect to you. 21.1.6 All Traffic In this Mode you will see all of the data packet traffic on channel. You can use this Mode to check that the TNC is working. 21.1.7 Information Packets In this Mode you will see all of the packet traffic on channel that contain information. You can use this Mode to check that the TNC is working. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 96 21.1.8 Single User Connects This is the normal one-on-one Mode of operation (USERS 1). 21.1.9 Multiple User Connects When you are in a Multiple Connect Mode, an asterisk will be shown in the status window next to the word "PACKET". Each I/O stream will show up in the Inwindow in a different color. LAN-LINK supports two multiple connect modes, Individual and Conference. An extract of an actual "off the air" CRT display (showing received text only) in a multi-user mode is shown below. Each line of text as received by the TNC is prefixed (by the PK-232) with the I/O channel number and callsign of the station its connected with. 1:4X4IL: *** CONNECTED to 4X4IL via 4X4IC, 4X6JP 0:4X4IC: joe do u read? 2:4Z4ZB: *** CONNECTED to 4Z4ZB 1:4X4IL: Look for me on PR via 4X6JP 73s and Shalom. 2:4Z4ZB: GE JOE I WILL DIS THEN U CAN GO VIA THE REP> 1: *** DISCONNECTED: 4X4IL via 4X4IC, 4X6JP 0:4X4IC: UNPROTO CQ 2:4Z4ZB: GO AHEAD BOYS...DE ALON..> 0:4X4IC: 2: *** DISCONNECTED: 4Z4ZB This is the normal Multi-connect Mode as described in the TNC manual. Here you are connected to up to 10 stations and will send different traffic to each of them. Each time you wish to send something to a particular station, you must select the I/O channel the station is connected on before typing the text or sending the file. The default stream change character for all TNCs in the VHF multiple connect modes is "|" ($7C). In the KAM, it is "\" on HF and "|" on VHF. They are both on the same key but one is in the shift case. Be careful on HF as the "\" shows up in file directories and confuses the computer. These values can be customized. However to do so, they must be customized both in LAN-LINK and in the TNC at the same time. You select the I/O channel using the Alt-N key and moving the cursor to the desired stream, or by typing the "|" character followed by (in the TNC) the channel letter/number. For example to do it manually, if you are connected to G8BTB on I/O channel 0 and to G3ZCZ on I/O channel 1, then to talk to G8BTB you would LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 97 type "|0" before any text, and similarly to send something to G3ZCZ you would type a "|1" before the text you"re going to send me. If you are not using a PK-232, read the TNC manual to deter- mine if the I/O streams are identified by numbers or by letters. The TNC2 standard configuration uses letters ("|A" etc.). Use the Alt-N key and move the cursor up and down to select the I/O channel automatically. 21.1.10 Conference In the Conference Mode on the other hand, everything that you type at the keyboard is automatically transmitted to each station that you are connected with. Thus if you are linked to two stations each line will be packeted twice by the TNC. You don't have to worry about sending the wrong thing to the wrong person, as they will all get the stuff. You enter this Mode by selecting the "F" option in the Terminal Menu. You terminate this Mode by selecting the "1" option. You connect in the usual manner using Alt-C or the Connect Option in the Call Menu. You must wait for a connection to be established, or to time out, before attempting to connect to the next station. If you do not, you will get an error message back from the TNC. In the Conference Mode, as the same text is transmitted on all I/O channels, the throughput will be reduced. Slow down your typing speed or use short packets. Should you check the link status or call monitored list, you may not be able to get back into the Converse Mode if you have too many packets outstanding. If that happens, wait a while and then try to set the Converse Mode with Function Key 10 (F10). You may have to try it a few times, depending on how good your links are. Don't try to send a file in the conference mode, it is not designed for it. Keep the packets short (use short lines). Be also warned that if you use the conference bridge on bad links (such as crowded HF channels, or VHF/UHF channels with lots of retries, the keyboard may seem to lock up. This is because LAN- LINK has to wait for space to appear in the TNC buffer before it can output the text. The Conference Mode will only work in the PK-232 if DCDCONN is set to ON. So if you are using a PK-232, LAN-LINK will do it for you when you enter the Conference Terminal Mode in case you forgot or/and haven't set the LAN-LINK.SYS file to include the line "DCD ON". At the same time set LAN-LINK.SYS default states to show the calls of other stations on each incoming line in the LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 98 Multiconnect modes (read the TNC manual on how to do this). The Conference Mode will only work in the TNC2 if DCDCONN is jumpered so that Pin 8 of the RS-232 Interface changes state when you connect to someone else. If you get error messages and see the characters "|J" on your screen, then the jumper probably isn't set. The Conference Mode does not work on the TNC1. In the Conference Mode, if any one of the stations disconnects, the TNC will return to the Command Mode, and you must use Function Key 10 (F10) to return to the Converse Mode before you type another character of text. 21.1.10 Conference Bridge ON/OFF This option toggles the Conference Bridge ON and OFF. In the Bridge Multiconnect Mode you are acting as a central switch. You can link together up to 10 stations in one multi-way connection. In this Mode any packets arriving on any stream are echoed to all other streams that you have "connects" on except the one that they came in on. Anything you type will be sent to all connected streams. In this manner, all stations will not see their own text echoed back. Each line of text output by LAN-LINK in this Mode will contain the callsign of the station originating the packet. Your packets will contain your call as entered in line 1 of the LAN- LINK.SYS file. Thus for example, if your call was KB8RP/4X and normally shows up in the packet header as KB8RP here it will show in the data as KB8RP/4X. Just remember that the Bridge puts out a lot of packets, so do multi-way connects on a quiet frequency. You must be in the Conference Mode to turn the bridge on, and any disconnect will take the bridge down. Should that happen, toggle it on again. A bridge will be shown in the status window whenever the Conference Bridge is up. 21.1.11 Turn Metabeacon ON/OFF This option lets you turn the LAN-LINK Metabeacon ON and OFF. LAN-LINK provides you with a metabeacon, that gives you the capability to transmit a long beacon message at periodic intervals. The Metabeacon is loaded from the contents of one of the LAN-LINK.00n files. These files may be created by the LAN- LINK editor. When loading, LAN-LINK will insert a pass character (^V) into the text before a carriage return, so as not to end the packet before at least 240 characters, and not more than 255 characters have been output to the TNC. The maximum number of characters that can be loaded into the Metabeacon is 1776. The LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 99 maximum number of packets in a Metabeacon is 7. You can also force a hard carriage return or "end of packet" in the Metabeacon by inserting the "\" (backslash) character, which will not be transmitted, into the text. The frequency of Metabeacon transmissions is the same as that of the automatic CQ timer. The MetaBeacon is designed for special event stations. PLEASE do not abuse it. 21.2 AMTOR Terminal Menu In the AMTOR Communications Mode, you are presented with the choices shown in Figure 21.2. Type in the single letter to make your choice. Figure 21.2 AMTOR Menu L Force LETTERS Case R Set ROBOT/Mailbox W CW Identification Z Set ROBOT Infinite Delay 21.2.1 Force LETTERS Case This option lets you force the PK-232 receiver to the letters case if for some reason you appear to be in the numbers case. It will return you to the Converse Mode. If your TNC allows you to use a control character (^L) to force the letters case, you don't need to go through all these menu layers to do the job. 21.2.2 Set ROBOT/Mailbox This option lets you turn on the Mailbox during a regular AMTOR QSO so that the other station can leave a message or download a file remotely. You must only use it when the other station is sending text. 21.2.3 CW Identification This option only works on the PK-232. You use it to send a CW identification (CWID). The CWID is sent in the FEC Mode. The CWID consists of the sequence "DE YOURCALLSIGN" where YOURCALLSIGN is that entered into the PK-232 as "MYCALL". You use this feature if your license requires you to identify in Morse code as well as in the operating mode. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 100 21.2.4 Set ROBOT Infinite Delay You use this option to prevent the Robot from ever transmitting when not linked. In the normal manner, the Robot counts down the CQ delay parameter, and, when it gets down to 0, puts a CQ call on the air. If the Infinite Delay is set, the CQ call will be inhibited. This option thus puts the Robot into an indefinite wait mode where it thinks it has sent out a CQ call and is waiting for a reply. You would use this Mode if you want to set up a MailBox on a known frequency for some group or organization. 21.3 Baudot Terminal Menu In the Baudot Communications Mode, you are presented with the choices shown in Figure 21.3. Type in the single letter to make your choice. 21.3.1 Set Baud Rate This feature allows you to set a desired communications baud rate directly. You will be prompted to enter the desired rate. Use this command to avoid having to shift through too many intermedi- ate states, if for example, you want to make a direct change from 45 to 100 baud. Figure 21.3 BAUDOT Menu B Set Baud Rate F Select Shift N Turn NAVY MARS Message Protocol ON U USOS OFF K Turn SELCAL ON W CW Identification 21.3.2 Select Shift This feature lets you select Wide (850 Hz) or narrow (170 Hz) shift directly. The PK-232 will copy 170 Hz signals using its internal 200 Hz circuitry. If you have a KAM, you may also select the Commercial Shift (425 Hz). The shift is displayed in the status window at the top of the screen. It is shown as "W"", "N" or "C" for wide, narrow or commercial respectively. 21.3.3 NAVY MARS Message Protocol The Navy MARS option toggles the Navy MARS Mode ON and OFF. When LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 101 the Navy MARS option is active, an "[N]" will be displayed in the status window, and the feature performs the protocol described below. 21.3.3.1: Any Carriage Return or Enter (CR) from the keyboard is sent as CR, CR. (two sequential CR characters. 21.3.3.2: In a file transmission lines are terminated by a CR, CR, LF (Line Feed) sequence. 21.3.3.3: In a file transmission, blank lines are sent as a LF (without a CR). 21.3.3.4: In a file transmission, a plus sign "+" in the file is replaced by a sequence of 12 "letters" characters. There can be more than one + sign on a line. 21.3.3.5: In a file transmission, the sequence "NNNN" is trans- mitted followed by a sequence of 12 "letters" charac- ters. There can only be one "NNNN" sequence on a line. 21.3.4 USOS ON/OFF This option toggles the Unshift on space (USOS) feature ON and OFF. When the USOS is on, the TNC reverts to the letters shift each time a "space" character is received. It helps when displaying noisy copy. If USOS is active, "USOS" will be shown in the status window at the top of the screen. 21.3.5 SELCAL ON/OFF This command key toggles the SELCAL feature ON and OFF. When the SELCAL is activated, as shown in the status window, the incoming text from the TNC is scanned. When either the letters "ZCZC" or "your callsign" (as entered in line 1 of the LAN- LINK.SYS file) is received, the "capture-to-disk" is turned on. All subsequent text will be stored in the LAN- LINK.RUN file until the letters "NNNN" are received. At that time the "capture-to-disk" is turned off. You may use this feature when monitoring commercial RTTY broadcasts to record news and other information, or when calling CQ to start recording all incoming text and keep the QSO on disk. You may use Function Key 1 (F1) to turn the capture to disk permanently on to override the automatic turnoff if you wish. 21.3.6 CW Identification This option is used to send a CW identification. You use this if your license requires you to identify in Morse Code as well as in the operating mode. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 102 The identification consists of the sequence "DE YOURCALLSIGN" where your callsign is that entered into the TNC as "MYCALL". 21.4 ASCII Terminal Menu In the ASCII Communications Mode, you are presented with the choices shown in Figure 21.4. Type in the single letter to make your choice. Figure 21.4 ASCII Menu B Set Baud Rate F Select Shift K Turn SELCAL ON W CW Identification 21.4.1 Set Baud Rate This feature allows you to set a desired communications baud rate directly. You will be prompted to enter the desired rate. Use this command to avoid having to shift through too many intermedi- ate states. For example, if you want to make a direct change from 110 to 1200 baud. 21.4.2 Select Shift This feature lets you select Wide (850 Hz) or narrow (170 Hz) shift directly. The PK-232 will copy 170 Hz signals using its internal 200 Hz circuitry. If you have a KAM, you may also select the Commercial Shift (425 Hz). The shift is displayed in the status window at the top of the screen. It is shown as "W", "N" or "C" for wide, narrow or commercial respectively. 21.4.3 SELCAL ON/OFF This command key toggles the SELCAL feature ON and OFF. When the SELCAL is activated, as shown in the status window, the incoming text from the TNC is scanned. When either the letters "ZCZC" or "YOURCALLSIGN" (as entered in line 1 of the LAN-LINK.SYS file) is received, the "capture-to-disk" is turned on. All subsequent text will be stored in the LAN-LINK.RUN disk file until the letters "NNNN" are received. At that time the "capture-to-disk" is turned off. You may use Function Key 1 (F1) to turn the capture to disk permanently on to override the automatic turnoff if you wish. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 103 21.4.4 CW Identification This option is used to send a CW identification. You use this if your license requires you to identify in Morse code as well as in the operating mode. The identification consists of the sequence "DE YOURCALLSIGN" where your callsign is that entered into the TNC as "MYCALL". 21.5 CW Menu In the CW Communications Mode, you are presented with the Menu shown in Figure 21.5. Type in the single letter to make your choice. Figure 21.5 CW Menu L Lock to Receive Signal S Set Morse Speed U Unlock Morse Speed X Turn XMIT Flag ON 21.5.1 Lock to Receive Signal This option locks the TNC to the speed of the incoming CW signal. 21.5.2 Set Morse Speed This option lets you set the CW speed. 21.5.3 Unlock Morse Speed This option unlocks the TNC from the incoming CW signal. It performs the same task as the Alt-D option keys. It is used to speed up capture of a new signal or to break the lock when the TNC appears to have locked up at the wrong speed. 21.6 Pactor Terminal Menu Pactor applies to the KAM and PK-232 only, assuming they contain Pactor firmware. In the Pactor Communications Mode, you are presented with the choices shown in Figure 21.6. Type in the single letter to make your choice. Do not use any of these options when linked to another station or you may drop the link. 21.6.1 AUTO BAUD This option configures the TNC to switch between 100 and 200 baud on the HF Pactor link as determined by propagation Conditions. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 104 Figure 21.6 Pactor Menu 0 AUTO BAUD 1 Force 100 BAUD 2 Force 200 BAUD H Enable Huffman K Disable Huffman 21.6.2 Force 100 Baud This option forces the TNC to use 100 baud on the HF Pactor link as determined by propagation Conditions. 21.6.3 Force 200 Baud This option forces the TNC to use 200 baud on the HF Pactor link as determined by propagation Conditions. This option is only available for the KAM. 21.6.4 Enable Huffman This option enables Huffman compression of the transmitted text. 21.6.5 Disable Huffman This option disables Huffman compression of the transmitted text. 22.0 EXIT TO DOS When you exit the program and return to DOS, if the Shut down (QRT) flag is set to 0, the TNC is put into the VHF default mode in which it rejects calls from any other stations. (Read about the CFROM and/or CONOK command in the TNC manual). You can, if you wish, leave the TNC powered, and, if you also leave the VHF radio powered up, you will be active as a digipeater, but at the same time anyone trying to connect with you will receive a "busy signal". The MBX command (Reading the Mail) is also cleared at this time. If you want to leave the TNC set up to accept messages when LAN- LINK is not active, customize the shut down state as described in the Section 18.23. 23.0 THE ELMER MENU ELMER is a smart server or second operator feature described in Appendix 7. The ELMER Menu presents you with the choices shown in Figure 23. Type in the single letter to make your choice. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 2 Page 105 Figure 23 The ELMER Menu C Change ELMER File E Turn ELMER ON/OFF L Load ELMER.QSO P Pick File to edit S Edit ELMER.QSO T show state Table 23.1 Change ELMER File This option allows you to change the ELMER state table file. 23.2 Turn ELMER ON/OFF This option allows you to turn ELMER ON and OFF. If the ELMER state table file (ELMER.QSO) is not present, you will not be able to activate ELMER. 23.3 Load State Table (ELMER.QSO) This option allows you to reload the state table. The name of the state table will appear in the menu. 23.4 Pick File to Edit This option allows you to pick and edit, a file with the default filetype of "TXT". 23.5 Edit State Table (ELMER.QSO) This option allows you to edit the state table. 23.6 Show State Table This option allows you to see the contents of the state machine. It is used in debugging the logic to ensure that the contents of the table match what you thought you put into it. A typical set of contents appears as shown in Figure 23.1. The keywords have been capitalized and set to 15 characters wide. None existent characters have been represented as periods. Figure 23.1 Typical ELMER State Table L C N R E KEYWORD U FILE 0 1 2 0 0 WHAT........... 0 * 1 2 3 0 0 ENGLISHMAN..... 0 * 3 3 4 0 0 DOING.......... 0 * 4 4 1 0 0 COUNTRY........ 0 ME-USA.TXT LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 106 Appendix 3 LAN-LINK Disk Files The following disk files are associated with the LAN-LINK program. LAN-LINK.COM LAN-LINK.SYS *.RUN LAN-LINK.LOG LAN-LINK.DIR CONFIG.SYS *.MBX *.BBS LAN-LINK.001 .. LAN-LINK.010 QBU-RX.BAT QBU-TX.BAT LAN-LINK.QTA QZ*.BAT ELMER.QSO LAN-LINK.OUT The "*" represents a "wildcard" character in the manner of DOS. Consider each file in turn. 1.0 LAN-LINK.EXE This is the program. You activate it from DOS by typing the word "LAN-LINK" followed by "ENTER" in the normal manner of invoking DOS commands. 2.0 LAN-LINK.SYS This file contains the configuration information for both the program and the TNC. Use the customization options in the parameters menu to make any changes not taken care of in the INSTALL program. The contents of the default file together with an item number are shown below. 1. Callsign 2. Selcal 3. CQ Text 4. CTEXT Line 5. ELMER Flag 6. CQ Delay (seconds) 7. CQ Delay (minutes) 8. :QSP: Message Relay Flag 9. PC Serial Communications Port Number 10. TNC Type LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 107 11. PC to TNC Baud Rate 12. VHF Log Book File 13. HF Log Book File 14. GMT Offset 15. Path Directory File name 16. Brag Tape File name 17. PBBS Snatch Mail Trigger Word 18. QTC Snatch Flag 19. PBBS Snatch Flag 20. Shut Down Mode 21. PC to TNC Data Bits 22. PC to TNC Parity Bit 23. PC to TNC Stop Bits 24. DCD Flag 25. QBM Download Sub-directory 26. Run File Directory Path 27. PBBS Read Request Command 28. Local PBBS Callsign 29. SAREX Callsign 30. SAREX Capture to Disk File name 31. PacketCluster Call 32. TNC Specific Parameters 33. Node Drop Link Flag 34. Sound Flag 35. Display Computer Generated Commands Flag 36. Date/timestamp in Call Sequence Flag 37. Keyboard Character Beep value. 38. :QBU: Receiving Station Batch file (QBU-RX.BAT) 39. :QBU: Originating Station Batch file (QBU-TX.BAT) 40. Capture-to-disk Flag 41. Beacon Control/LAN-LINK handshake Flag 42. Read Bulletin Character 43. PBBS Subject String 44. PBBS Message String 45. VHF Paclen 46. HF Paclen 47. Beacon Time 48. Number of CQ Lines 49. Word wrap 50. PC Port 4 Custom Address 51. PC Port 4 Custom IRQ 52. VHF Stream switch character 53. HF Stream switch character 54. TNC Error message 55. Connect Timeout Delay 56. Custom Prompt 57. ELMER Configuration File 58. Expand Transmitted File flag 59. Input Message Base Count 60. Default users LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 108 61-88. Custom Colors 89. First PacketCluster Command 90. Second PacketCluster Command 91. TNC Mailbox ON Command 92. TNC Mailbox OFF Command 93. VHF Maxframe Command 94. HF Maxframe Command 95 Inhibit VHF Logging Flag 96 Inhibit HF Logging Flag 97 Printer Permanent Flag 98 Log Disk Update Flag 99 Secondary Log Flag 100 Auto Answer Flag 101 RUN File Disk Update Flag 102 Default CW Speed 103 Secondary Logbook 104 BBS List Command 105 BBS List Mine Command 106 BBS Custom Command 107 BBS Bye Command 108 Start Up Packet Terminal Mode 109 Page Time (:QIC: Seconds) 110 Packet Cluster DX Alert Tone CW Dit time 111 Packet Cluster DX Alert Tone CW Note 112 Packet Cluster DX Alert Mode 113 Mode File Flag 114 BAUDOT Color Change Text String 115. Start of Scan Words (MUST HAVE AT LEAST ONE) 116. * end of Scan Words 117. Start of Common Calls (MUST HAVE AT LEAST ONE) 118. * end of Common Calls 119. Remaining TNC start up Commands. The contents of each line are described in the section of the Parameters menu which deals with customizing them. The others, described below, can only be changed by using the Editor. The remaining lines contain commands to the TNC. For further informa- tion about them refer to the TNC manual. LAN-LINK assumes different defaults (in some instances) to those set in the TNC. The LAN-LINK.SYS file contains only those that are different to the TNC default reset state. 2.1 CTEXT Line This parameter is the CTEXT line changed in the TNC Menu. 2.2 ELMER Flag This parameter is the ELMER Flag. If it is a "1", ELMER is primed for activity. ELMER is only active in the Packet communications LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 109 mode, when you are connected to another station. If the ELMER flag is a "0", or the ELMER state table file is not present in the default directory, LAN-LINK will never activate ELMER. 2.3 PC Port 4 Custom Address This parameter is the decimal value of the address of your Port 4. Use this parameter if you are using a non standard Serial I/O card. Configure the PC Port to 4. The PC default address for Com4 is 2E8 (hex) or 744 (decimal). 2.4 PC Port 4 Custom IRQ This parameter is the decimal value of the IRQ of your Port 4. Use this parameter if you are using a non standard Serial I/O card. Configure the PC Port to 4. The PC default IRQ for Com4 is 3. 2.5 VHF Stream Switch Character This parameter is the VHF stream switch character. If you wish to change it, you must enter the ASCII representation in this line, and the equivalent stream switch command in the LAN-LINK.SYS file. 2.6 HF Stream Switch Character This parameter is the HF stream switch character. If you wish to change it, you must enter the ASCII representation in this line, and the equivalent stream switch command in the LAN-LINK.SYS file. The KAM is currently the only TNC that has different HF and VHF stream switch characters. 2.7 TNC Error Message This parameter is the error message your TNC generates. The PK- 232 generates "?What?". Others may generate "EV?" or "?EH". 2.8 Connect Timeout Delay This parameter is the time, in minutes, LAN-LINK lets you stay connected to another packet station, after the receipt of the last incoming character. 2.9 ELMER Configuration File This parameter is the name of the default ELMER Configuration file. It is changed through the ELMER Menu. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 110 2.10 Expand Transmitted Files Flag The Flag tells LAN-LINK to scan the outgoing text when a file is transmitted and perform the same conversions it does to the contest text. You can insert the '##', "#1' and "#T" parameters in the files to transmit, your call sign, the other station's call, and the time of day. Set this parameter to 1 to enable the feature, 0 to disable it. 2.11 First PacketCluster Command This parameter is the first command (up to 20 characters) LAN- LINK sends to the PacketCluster after receiving a ">" character at the end of line from the PacketCluster. 2.12 Second PacketCluster Command This parameter is the second command (up to 20 characters) LAN- LINK sends to the PacketCluster after receiving a ">" character at the end of line from the PacketCluster. 2.13 TNC Mailbox ON Command This parameter is the command (up to 15 characters) your TNC expects to turn its internal mailbox ON. 2.14 TNC Mailbox OFF Command This parameter is the command (up to 15 characters) your TNC expects to turn its internal mailbox OFF. 2.15 VHF Maxframe Command This parameter is the command (up to 15 characters) your TNC expects to set the VHF MAXFRAME parameter. 2.16 HF Maxframe Command This parameter is the command (up to 15 characters) your TNC expects to set the HF MAXFRAME parameter. 2.17 Inhibit VHF Logging Flag When set to 1, automatic VHF Logging is disabled. 2.18 Inhibit HF Logging Flag When set to 1, automatic HF Logging is disabled. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 111 2.19 Printer Permanent Flag When clear (set to 0), if you leave the printer on during a packet connect, it will stop printing when you disconnect. This stops the printer generating lots of garbage. If you set this parameter to 1, the printer will not stop printing when you disconnect. 2.20 Log Disk Update Flag If this flag is set to 1, LAN-LINK writes each log entry to disk as you enter it. If this flag is not set (=0), LAN-LINK writes the log entry to a buffer and updates the disk when the program is terminated. Set the flag ON to ensure that rare DX contact is logged, Set it OFF for speed, or if power dropouts are not a problem in your area. 2.21 Secondary Log Flag If this Flag is set to 1, LAN-LINK allows you to search both the current log book and a secondary logbook for the call of a station. 2.22 Auto Answer Flag If this flag is set to 1, AND you have a LAN-LINK.OUT file on your system, LAN-LINK will transmit the contents of the LAN- LINK.OUT file to every incoming connection. 2.23 Ctdsk File Disk Update Flag If this flag is set to 1, LAN-LINK will close the capture-to-disk file (YYMMDD.RUN) between received messages. If the flag is not set, LAN-LINK will close the file when all messages have been received, or a DISCONNECT takes place. 2.24 Default CW Speed This is the default CW speed for the multi-mode TNC (KAM, PK-232 or MFJ1278). 2.25 Secondary Logbook This is the name of the secondary logbook. 2.26 BBS List Command This is the BBS List Command. The default value is 'L'. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 112 2.27 BBS List Mine Command This is the BBS List Mine Command. The default value is 'LM'. 2.28 BBS Custom Command This is a configurable BBS List Command. The default value is 'KM'. 2.29 BBS Bye Command This is the BBS Bye Command. Change this parameter when the default 'B' command only drops you to the Node. 2.30 Start Up Packet Terminal Mode This is the Packet Terminal Mode when LAN-LINK is first activated. Set this to the letter corresponding to the terminal mode you like being in. See Section 21.1. Use the corresponding letter, as shown in Table 2.30. Table 2.30 Start Up Terminal Mode Letter Mode Actions I INFO lets you only see packets containing information. S SOLO lets you only see messages addressed to you. C CQ/B lets you see beacons and CQ calls as well. T TRFC lets you see packets containing messages as well. E EVRY lets you see everything on channel, including the link control packets. 2.31 Page Time (:QIC: Seconds) This is the number of seconds the system pages the operator in response to a QIC command, if the sound is turned on. 2.32 PacketCluster DX Alert Tone CW Dit time This is the time period for 1 dit sound in the PacketCluster audible DX alert message. 2.33 Packet Cluster DX Alert Tone CW Note This is the tone for the PacketCluster audible DX alert message. 2.34 Mode File Flag If this flag is set, LAN-LINK will change the name of the LAN- LINK.001 to LAN-LINK.010 when you change communications modes. The name will change to the mode followed by a number, i.e LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 113 BAUDOT.001 to BAUDOT.002, or AMTOR.001 to AMTOR.002. 2.35 BAUDOT Color Change Text String This is a pair of characters that LAN-LINK will scan text appearing in the incoming window for. When LAN-LINK recognizes the pair, it will change colors. This parameter is customizable to allow you to override apparent random changes of color, since there is no agreed standard way for signalling 'over' in BAUDOT. 2.36 TNC Parameters The remaining lines contain parameters loaded into the TNC at initialization. If you are not using a TNC1 you MUST set the HEADERLN parameter to ON. The packet headers and the text of the packets must show up on your screen on separate lines. You must also have the "Echo as Sent" feature set ON ("EAS ON" for PK-232 and "XM" ON " for the KAM). 3.0 *.RUN These files contain incoming data from the TNC recorded while the "capture-to-disk" function was active. LAN-LINK names them as YYMMDD.RUN automatically (YY = Year, MM = Month, DD = Date, i.e. 920903.RUN is a file for 3 Sept 1992). 4.0 *.DBF (HF.DBF and VHF.DBF) These file contain the log entries. They are Dbase 3 and 4 compatible. The format of the logbook file is the same as that used by the LOGBOOK package of the PC-HAM software package, with a little additional space for comments. 5.0 LAN-LINK.DIR This is the directory file as described in Appendix 2, Section 6.1.2. You use it to store names, handles, NET/ROM, TheNet, KA- Node, ROSE or digipeat paths as well as name/callsign relation- ships. Sample lines are shown below. Joe G3ZCZ Alon 4Z4ZB V 4X6AA Milt 4X6AA LR 4X6LR hf-il 4x4hf v 4z4zb 4x4il hf-rj 4x4hf v 4z4zb 4z4rj K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT!K1HTV w9tnn-2 jrw !% w3eax-7 !& w9tnn-2 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 114 You create this file with the Editor or by using your word processor in its non-document mode. You must leave at least one space character between the first (key) word and the connect path. When you type in the key word, the program does not care about upper or lower case. You may also use the "reMember Path" option in the Call Menu to make entries in this file. If you already have a YAPP.DIR or a PK232COM.DIR file just rename it to LAN-LINK.DIR and add any NET/ROM and/or KA-Node paths. All path entries in LAN-LINK.DIR must be on a single 80 column line. 6.0 CONFIG.SYS You must have a CONFIG.SYS file on the boot disk if you are going to use the disk logging features. This file must contain the line FILES = 20. See the DOS manual for more information about the CONFIG.SYS file. 7.0 *.MBX These are the files associated with the stations you have designated as LAN store and forward mailboxes. Other stations can only :QRU: with you if you have designated them as QRU stations and have a "CALLSIGN.MBX" file on your disk. For example, if you want to use 4Z4ZB as a store and forward mailbox, you will have to create an ASCII file called 4Z4ZB.MBX using Editor, or the non-document mode of your word processor. In this file you will put a list of the call signs of the stations 4Z4ZB can connect with reliably. For example, if you want 4Z4ZB to be able to store messages from you to 4X6AA, 4X6LR, G3ZCZ, ON8IK, F0WN,and G8BTB, you would put those call signs in the file, one call on a line as follows. 4X6AA 4X6LR G3ZCZ ON8IK F0WN G8BTB When the QRU function is invoked either by you manually or by 4Z4ZB connecting to you and sending you the command :QRU:, any LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 115 message files present on your system addressed to any of those stations (E.G. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as if you had tried to :QSP: the messages manually or as if G3ZCZ or ON8IK had connected directly to you. The file names on your system will be changed to *.OLD. You must create one file for each designated store and forward station, i.e. 4Z4ZB.MBX, G3ZCZ.MBX etc. 8.0 *.BBS These are LOCAL-BBS.BBS AUTO-Upload Command files. Each file is named for the callsign of the BBS that you wish to access. It must have exactly the name as the callsign of the BBS. If the BBS is W9TNN-1 the name of the file must be W9TNN-1.BBS, or if the BBS is 4Z4ZB then the file must be called 4Z4ZB.BBS. The file must be an ASCII file. that means the word processor must be used in the non-document mode to create it. This file contains the command sequence that you would have typed at the keyboard if you were accessing the BBS manually. The ONE difference is that the text of a message you are uploading with the S command must be followed by the character strings ":EOF:" or "/EX" (on a separate line) as illustrated by the example below. If you use the "D" command to download a text file, the file will end up in a separate file on your disk ONLY IF a file of the same name does not exist on your drive. Do delete "read" mail from your local PBBS. Don't clutter the PBBS's disk with your read mail. The "LM" command is built into LAN-LINK to remind you of what you have out there. The PBBS "S" command (including its variations such as "SP") is the only multiple line command allowed. You can put all the single line commands such as "D", "H", "?", "L", and "R" in the PBBS.BBS file. A "multiple command" is defined in this instance as a command which allows you to enter multiple lines before the PBBS will send back a ">" character (i.e. one that the PBBS tells you to type in text and terminate it with the Control-Z (^Z) character). A typical message could be as shown below. SP G3ZCZ @ N4QQ LAN-LINK I think it is great. However, why don't you change the following...... (add your comments here). LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 116 73 de your name :EOF: {last line may also be "/EX"} k 1234 d \net\lan-link.doc s g8btb Test Message This is a test message. :EOF: lm r 567 r 593 9.0 LAN-LINK.001 - LAN-LINK.010 These are 10 different text files with fixed names. They can be transmitted using the Alternate function keys. Their contents can be viewed using the Shift function keys. In all cases the function key to use for a particular file corresponds to the number in the file suffix. For example, use Alt/Shift Function Key 3 (Alt-F3) to transmit/view file LAN-LINK.003. You may also use the Edit Menu to edit and/or create the files. In case you forget what you put in each of the files, LAN- LINK allows you to take a peek into all of them at the same time. Use Control Function key 1 (Control-F1) to look at the first line of all the LAN-LINK.001 - LAN-LINK.010 files and the Brag Tape. If the Mode File flag is set, LAN-LINK changes the files as you change modes. You thus have 10 files in EACH mode, accessable via the same set of control function keys. The file names are shown below. COMMUNICATIONS MODE Mode Flag FILE NAMES All OFF LAN-LINK.001 to LAN-LINK.010 Packet ON LAN-LINK.001 to LAN-LINK.010 AMTOR ON AMTOR.001 to AMTOR.010 BAUDOT ON BAUDOT.001 to BAUDOT.010 ASCII ON ASCII.001 to ASCII.010 CW ON MORSE.001 to MORSE.010 Pactor ON PACTOR.001 to PACTOR.010 10.0 QBU-RX.BAT This is the command or batch file used in the :QBU: originating station. 11.0 QBU-TX.BAT This is the command or batch file used in the :QBU: receiving station. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 117 12.0 LAN-LINK.QTA You can leave a message on your system for someone else in a file named CALLSIGN.OUT. When the station with that callsign connects to you, the message will be sent, and the filename will be changed from CALLSIGN.OUT to CALLSIGN.OLD. This is fine as long as the path between the stations good. If the path is marginal, it is possible that your station will transmit the message and change the filename, but the link will drop out before the message is received at the other station. If the other station does not connect to you and :QSM:, the message may get lost. If this situation occurs, you can tell LAN-LINK that there is a bad path between you and that station, and not to change the file names without an explicit :QTA: instruction from that other station. You do this by putting the call of the station(s) having a bad path in an ASCII file called LAN-LINK.QTA. Put one call on each line in the form N9BE G8BTB You must use the root call of the station without an SSID. that means, if the station is N9BE-4, just put N9BE in the file. LAN-LINK will automatically acknowledge incoming messages from stations with callsigns in the LAN-LINK.QTA file with a ":QTA:". 13.0 QZ*.BAT As any LAN-LINK station can either receive or originate a :QZD: and a :QZU: command, LAN-LINK uses four batch files to control Zmodem transfers. These files are as follows. QZU-RX.BAT Batch file implemented after receipt of :QZU: QZU-TX.BAT Batch file implemented after transmission of :QZU: QZD-RX.BAT Batch file implemented after receipt of :QZD: QZD-TX.BAT Batch file implemented after transmission of :QZD: Each LAN-LINK user must configure the QZ*.BAT files for their systems. The port number in the batch file should be set to the PC I/O Port used. The data rate in the batch file should be set to the data rate used between the PC and the TNC, NOT the data rate used on the radio link. For example, the default QZU-RX.BAT file of "pcz 1 1200 rz %1" should be changed to "pcz 2 1200 rz %1" if you are have interfaced your TNC to Port 2 on your PC. If, the baud rate between the TNC is 2400 baud, the file should be changed to "pcz 2 2400 rz %1". LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 3 Page 118 Each of the four batch files have to be customized for each user who is not using PC Port Com1 and 1200 baud between the PC and their TNC. The INSTALL program takes care of that chore. The high level of customization required here is because different Zmodem implementations require different sequences of instructions and LAN-LINK does not want to limit you to a specific one. 14.0 ELMER.QSO This is the state table (configuration file) for ELMER. The contents of the file are as described in Appendix 8. If this file is not present in the same sub-directory as LAN-LINK, you will not be able to activate ELMER. 15.0 LAN-LINK.OUT This file will be transmitted to all incoming connects (except when in the multi user mode), if the file is present, and if the Auto Answer flag is enabled. You can think of this file as a CTEXT File. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 119 Appendix 4 Local Area Network Capability VHF Packet radio systems can be considered as part of a Local Area Network (LAN) in which messages can be left by one station in the computer belonging to a second station. At HF the same is true, but the area becomes greater. The basic problem here is that people can only send and receive messages to or from you when you are on-line. To compensate for this, BBS stations were developed which allowed both messages and bulletins to be stored by anyone for later retrieval. LAN-LINK allows you to store messages in your computer so as to use it as an automatic answering machine. By storing the messages in a file called by the name of callsign, with the file extension ".OUT", anyone connecting to the computer will get their message without having to request it. LAN-LINK also extends that concept to cover the eventuality of you wanting to take your computer off-line for some reason. You may now load the message into any other computer you can connect to using elements of the Q code adapted to the High Level Network Communications Language (NC/L) first proposed in my book Software for Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 U.S.A. 1.0 LAN Protocol (G3ZCZ Version) The protocol is as follows. When connected to someone who has their LAN-LINK configured as a host, if you want to store a message on that system, you use "QSP". You send the other station ":QSP: CALLSIGN" where "CALLSIGN" is the callsign of the station that the message is for, not the callsign of the host station in whose computer you are storing the message. [Note use only one space character after the :QSP:]. For example if you want to store a message for 4Z4ZB in 4X6AA's computer which is configured as a LAN-LINK Store and Forward system, you would first connect to 4X6AA and then send the command as ":QSP: 4Z4ZB". Better still use :QSP: option in the Lan-Link Menu to automate the sequence. The computer at 4X6AA will respond either with a statement saying that it is ready for you to go ahead, or send a message saying that it can't comply. If it is ready you get a positive reply which will take the form :QRV: CALLSIGN which if you know the Q code, means "I am ready to accept a message for CALLSIGN". At this time you may go ahead and send the message. If you type the message at the keyboard, you may use either a Control-Z (^Z) character or the character sequence ":EOF:" followed by a carriage return (the "Enter" key) to terminate the message. If LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 120 you have first written the message into a text file you may then send it using the "Send File" option of the Files Menu and the termination sequence is automatic. Once you have completed the message, the other (host) computer will either reply that the message has been successfully stored or give you an error message. If the message is stored and ready to be sent next time the addressee connects to that computer, you will see the message :QSL: on your screen. If something went wrong, you will get back a negative message taking the form :QNO: followed by a number. The number tells you why the operation failed. 2.0 Message Format The message is stored just as if you had left it in your system (except that a header is added identifying the time of reception and the call of the sending station). It will contain a header showing the date and time it was received and your callsign. Should a message for that station already be in the system, yours will be appended to it. In the event your upload is aborted, the amount of text received before the abort occurred will be stored as the message. When you disconnect from the other LAN-LINK host station, its mail beacon will be updated. Once the message is loaded in the host, it can only be deleted by the operator of the host station. When the addressee connects to the host and receives the message, the file type will change from ".OUT" to ".OLD". Note QTA stations require positive confirmation of receipt of message for the renaming to take place. 3.0 ASCII File Uploading/Downloading There comes a time when you want to leave a file on your system for someone to download later. You can do this by using NC/L to control the transfer. You must leave the file in the file download sub-directory defined in the LAN-LINK.SYS FILE (default value is C:\LAN-LINK\FILES). You must first create the sub- directory, if it does not exist. The station who wants the message then asks for it using :QBM: FILENAME.TYP. They do not need to use the full sub-directory path. They must, however, leave a single space character between :QBM: and the filename. In AMTOR the Mailbox must be turned on for remote functions. For example, you have the latest ARRL DX bulletin, and you want to pass it on. You could pass it to selected people by copying the file to individual messages with the filetype ".OUT", e.g. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 121 4X6AA.OUT, 4Z4ZB.OUT or even G3ZCZ.OUT if you want me to get it, which wastes a lot of disk space. On the other hand you could tell people that the file was available for downloading, either in the CTEXT connect message line which everyone gets when connecting to you by configuring LAN-LINK accordingly, or in individual (".OUT") messages. If you include the following in your CTEXT message "ARRLDX.015 now available" people will know that to download it, they just have to type the line ":QBM: ARRLDX.015" (one space character between :QBM: and the file name) to get the file. LAN-LINK is not designed as a BBS, however, if you copy the contents of the \LAN-LINK\FILES sub-directory into a file called DIR (USE DIR > DIR in DOS), anyone can get a list of the files you have stored in it for downloading by typing :QBM: DIR. Since they do not get the real directory, just what was in it at the time you copied it into the file "DIR", you may keep "hidden" files in this sub-directory. You may thus leave a file for someone to download, tell them that its there by leaving them a message (which they will get automatically when they connect) and no one else connecting will know that it is there. If you want to upload a file, ":QDB:" allows you to upload text or ASCII files. If you use the "lan-linK" option of the Packet Terminal Menu, LAN-LINK will automate the QDB and QBM features for you. 4.0 Path Determination to a DX station If you want to establish a digipeat path to a station somewhat out of your direct range, you need to know which of the stations that you can connect to can hear that desired DX station. If you could get a call monitored (MH list) from the stations that you connect to, you would be able to see if the station you are connected to has heard your desired DX station. LAN-LINK uses the :QMH: command to request such a list. When LAN- LINK receives a :QMH: command, it drops back to the TNC Command Mode and issues a "MH" command to the TNC (except to a TNC1 which does not support it). It stores the list received in a temporary buffer, and then returns to the Converse Mode and transmits the list back to the station it is linked to. By judicious use of :QMH: you can determine paths to other stations. Note however, that just because one station can hear LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 122 another station, it does not mean that it can work it. For example, the station you are connected to may be using a power level of 1 watt or so, while the station 200 miles away that it heard was using 100 watts. Test the path yourself, or/and leave a message asking how reliable the connect path between those two stations is. If you and a small group use a non standard packet channel for inter-group communications, you may also use the :QMH: function to find out who the station you are connected with, has heard recently, when you first sign on the LAN channel. 5.0 Binary File Transfers In the PC world most binary file transfers seem to be taking place using the YAPP protocol built into the YAPP user terminal program and the BBS software written by Jeff Jacobsen, WA7MBL. As Jeff stated in the documentation, YAPP was written to provide a terminal program for use in testing the WA7MBL BBS code. However for many radio amateurs, YAPP was their first terminal program. The YAPP binary transfer protocol is similar to the Xmodem protocol used on telephone line BBSs. In order to transmit a file, the sending station breaks the file down into blocks of characters. Each block is transmitted in sequence. After a block has been transmitted, the sending station waits for the receiving station to acknowledge that block and verify that it was received without errors. When two stations are alone on a frequency, they can transfer data quite quickly. So back in 1986 when YAPP was written, it provided the few hams using packet radio with a binary file transfer capability. Today, however, the situation is different. In most urban areas, each packet radio channel is occupied by many stations, and the requirements for binary file transfers are somewhat different. 6.0 Requirements for Transfer Protocols The AX.25 protocol provides for a basic verification that packets have been received error free. If the binary file transfer protocol could establish the connection, start sending blocks, and then keep sending data until one of three things happen; the link drops out, the receiving station signals that some of the data were received with errors, or the whole file is transmitted correctly. If the whole file is transmitted, then the sending station just has to wait for an acknowledgment from the receiving station that the file was received. If the circuit is busy with several LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 123 stations on the channel, or the path goes through one or more Nodes, there will be varying delays in the delivery time of the packets. By not having to acknowledge each block of data, the file can get through much faster than it would have, in the case in which each received block has to be individually acknowledged. If the link drops out, it would be nice if the computers, could determine how much of the file was received, then pick up the transmission at that point next time they link up. If the receiving station signals that some data were received in error, the sending station should then begin to retransmit from the start of the error. 7.0 The Zmodem Protocol This situation is not unique to the amateur radio packet network. It is also present in the commercial packet switching environment, and the Zmodem protocol was developed to provide the capabilities described above. Zmodem thus seems to be an almost ideal binary file transfer protocol for use on radio amateur packet channels, and is incorporated in LAN-LINK 2.00+. LAN-LINK uses the :QZD: and :QZU: commands to provide the capability to remotely download and upload binary files. :QZD: allows you to download a file from another station, while :QZU: allows you to upload a binary file. :QZD: is configured so that if the link drops outs during the transfer, when the connection is once again established, a subsequent :QZD: for the same filename, will cause the transfer to pick up where it left off when the link dropped out. This feature is not allowed in the upload :QZU: command to inhibit people from injuring files that already exist on the other computer. Each command may be initiated from either end of the link, but to gain the most from the recovery capability, files should be downloaded by the receiving station. 8.0 The PCZ Zmodem Package LAN-LINK implements the Zmodem protocols using batch files in DOS that call up external programs. This approach allows stations to try different versions of Zmodem and experiment to find the optimal one for their area. LAN-LINK comes with the (PCZ) Public Domain implementation of the Zmodem, Ymodem, Xmodem, Xmodem-1K and Sealink protocols by Drue Kennon and Gary Smith. Since any LAN-LINK station can either receive or originate a :QZD: and a :QZU: command, LAN-LINK comes with four default batch files to control Zmodem transfers. These files are as follows. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 124 QZU-RX.BAT Batch file implemented after receipt of :QZU: QZU-TX.BAT Batch file implemented after transmission of :QZU: QZD-RX.BAT Batch file implemented after receipt of :QZD: QZD-TX.BAT Batch file implemented after transmission of :QZD: Each pair of users can experiment with other protocols and Zmodem implementations using the :QZD: and :QZU: commands after reading the PCZ documentation. The :QBU: command can also be used if the corresponding DOS batch files (QBU-RX.BAT and QBU-TX.BAT) are created. LAN-LINK contains an output buffer to store data being output to the TNC. The TNC contains a buffer which stores data about to be sent on the radio link. In the normal course of events, the two buffers fill up, so that the Zmodem package used by LAN-LINK may think that all the data has been transmitted, when in fact there are still characters left in the buffers, or the last packet has not yet made it to the destination station. In this case, you may see a message on your screen that the system has sent all the data and is waiting for the final acknowledgment, while at the same time you can see from the LEDs on the TNC that you still have outgoing data in your system. Have patience and wait a while to let the two systems synchronize. In the event that the link is bad and errors occur, this buffering may cause problems which require some of the Zmodem timing parameters to be changed. Should this situation arise, read the Zmodem package documentation. The flexibility offered by the Zmodem protocol has many advantages when used in a packet radio network. LAN-LINK 2.00+ implements Zmodem by the use of an external public domain protocol package which provides for the maximum degree of user customization. This capability is provided at the cost of having the individual user customize four batch files using the text editor built into LAN-LINK. 9.0 BASIC NC/L DICTIONARY Messages can be transferred into any other LAN-LINK computer you can connect with using elements of the Q code adapted for the purpose. NC/L command words are summarized in the following paragraphs. There is no command word to request your message. To receive your message, you do nothing. You will receive your mail automatically when connecting/linking with a LAN-LINK station. You cannot normally read messages addressed to another person. 9.1 :QBM: To download an ASCII file, send ":QBM: file name.type". The LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 125 filename.type is the file you want. i.e. ":QBM: DIR". 9.2 :QDB: To upload ASCII files to another LAN-LINK system send ":QDB: filename.type". Files will be uploaded into the same sub- directory as LAN-LINK, and will have a message header inserted at the top of the file to allow the operator to know who uploaded the file. If the operator then wants to make the file available for downloading, he or she can move it to the \LAN- LINK\FILES sub-directory. The ".TYP" following the filename is optional. If you attempt to upload a file which has the same name as one that already exists on the remote system, you will receive an "error" message. This command is the reverse of :QBM:. 9.3 :QMH: To request a call monitored list ("MH") from the LAN-LINK station that you are connected with, send ":QMH:". 9.4 :QSM: To request a repeat of a message from a station using LAN- LINK, send ":QSM:". This command will be valid as long as the host station has not deleted the YOURCALL.OLD file on his disk. If the file does not exist, you will receive a :QNO: "error" response. 9.5 :QSP: To leave a message, send ":QSP: callsign". The callsign is that of the station you wish to leave a message for. 9.6 :QRA: When disconnected, to see what stations (using LAN-LINK 1.53+) are on the LAN, or which LAN-LINK stations have messages pending, send ":QRA:". All LAN-LINK stations will reply with a mail beacon within a few seconds. The Alt-W key implements this feature. 9.7 :QRT: To shut down a LAN-LINK AMTOR/Packet mode Mailbox or beacon station which is causing QRM, link or connect to the station and send ":QRT:". 9.8 :QRU: To upload messages from one LAN-LINK/PK232COM (1.38+) system to your computer, send ":QRU:". LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 126 You may only use the QRU function with stations designated as Store and Forward mailboxes. Put a list of stations that you can connect to reliably in your CALLSIGN.MBX file and send it to other stations in your LAN also using LAN-LINK. They will then be able to dump their mail messages on you and you on them. If they do the same and send you their file, then you will be able to send messages via them for stations that they can work. While QRU gives you the capability to bulk upload messages to another station in your local area, when you take your machine off line, it may also be used to transfer messages between two LANs via well sighted gateway digipeaters. 9.9 :QNO: :QNO: and error message text is a response to a request. 9.10 :QJG: :QJG: is a response to :QRU:. It confirms that the QRU sequence is complete. There are no more messages pending. 9.11 :QRV: :QRV: callsign is a response to :QSP: callsign. The computer is ready to send the message. End the message with a control Z (^Z) character, or the sequence :EOF: 9.12 :QSL: :QSL: is a response to a command. It confirms receipt of message to that callsign or that a file has been successfully uploaded and stored to disk. It is also used to acknowledge receipt of a ":QRT:" command. 9.13 :QTA: message If LAN-LINK receives :QTA: and a message exists for the connecting station, LAN-LINK will change the filetype from "OUT" to "OLD" and respond with a "QSL". If a message does not exist, it will respond with a "QNO". 9.14 :QTC: Message List If LAN-LINK receives :QTC: it will respond with the beacon text showing the mail queue. :QTC: precedes a list of callsigns for whom messages are stored up on a computer. It is used in Packet Beacon transmissions or AMTOR Beacon mode CQ calls. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 4 Page 127 9.15 :QBU: External Protocols This feature is supplied to allow experimentation with external protocols. 9.16 :QZU: Zmodem Binary File Upload :QZU: is used to implement an upload of a binary file from another station using an external Zmodem protocol via the QZ*.BAT files. 9.17 :QZD: Zmodem Binary File download :QZD: is used to implement a remote download of a binary file from another station using an external Zmodem protocol via the QZ*.BAT files. In the event that the link drops out during the transmission, when the link is remade, and the :QZD: retried, the transfer will pick up from the point at which it was interrupted, if the batch files provided are used. 9.18 :QIC: Page Operator Use :QIC: to page the operator at any LAN-LINK 2.10+ station. The sequence is:- you send :QIC: to another LAN-LINK 2.10 station. Use the LAN-LINK Menu or type it by hand. Upon receipt, LAN-LINK begins to page the operator if the sound flag is on. At that time it sends you a :QRX: followed by a number, i.e. ':QRX: 30'. The number is the number of seconds it will page the operator. At the end of the paging sequence it will send the prompt i.e. 'G3ZCZ>'. If the sound is inhibited it will send ':QRX: QRT' to signal that it is in a silent configuration. 9.19 :QTR: Ask for Time The :QTR: command allows you to get the date-time-text string from the other LAN-LINK 2.10+ station. Don't confuse it with :QRT:. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 5 Page 128 Appendix 5 Using Different TNCs The Packet Mode capabilities can be used on all TNCs. There are minor differences in the command dialogue between different TNCs. The dialogue differences affecting the operation of LAN-LINK are built into the program and set when the TNC type is read from the LAN-LINK.SYS file at the program load time. The non packet modes will obviously result in error messages if attempted on a packet mode only TNC. The following notes apply to different TNCs or digital communications controllers. 1.0 TNC2 (MFJ 1270) The following functions do not work because the TNC does not support them. All NON PACKET modes. Software controlled HF/VHF switching. Software controlled baudrate switching. CQ/BEACON Packet terminal mode. TNC Transmit Buffer flush. N2GNJ noticed that he needed "LC ON" when using a Tiny 2 EPROM Version 2.0 in the MFJ 1270B to make the automatic snatch features work. 2.0 TNC1 (HK-4040) The Packet Communications Mode header colors are not supported in LAN-LINK for this TNC. The following functions do not work because the TNC does not support them. All NON PACKET modes. Day/Time functions. MH and remote :QMH: functions. MAIL Packet Terminal Mode. CQ/BEACON Packet Terminal Mode. TNC Transmit Buffer flush. Conference and multiconnect modes. 3.0 Kantronics KPC-2 The Packet Communications Mode header colors are not supported in LAN-LINK for this TNC. The following functions do not work because the TNC does not LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 5 Page 129 support them. All NON PACKET modes. MAIL Packet Terminal Mode. CQ/BEACON Packet Terminal Mode. TNC Transmit Buffer flush. 4.0 Kantronics KAM LAN-LINK switches colors when it sees the /V or /H following the callsign in the packet header, or in the calls monitored ("MH") list. If you are monitoring both HF and VHF simultaneously, the colors will show you which radio you heard which signal on. If the Mail-Snatch or the QTC-Snatch are triggered, LAN-LINK will change modes and attempt the connect on the correct radio but will not change the band/power information or the logbook to reflect that change in the logbook or in the status window display. Turn the DCD flag OFF for these automatic features to work. The following functions do not work because the TNC does not support them. TNC Transmit Buffer flush. The SIGNAL Communications Mode. The Alt-D key in the MORSE Communications Mode. The AMSAT-OSCAR Menu does not allow UoSAT option, as the KAM does not have 1200 baud ASCII capability. 5.0 PK-232 Turn BBS OFF, if you want the Alert Call, packet communications mode header colors, and Digipeat Detect features to work, otherwise turn BBS ON. 6.0 MFJ 1278 LAN-LINK assumes that the Radio 1 port is connected to the VHF/UHF packet transceiver, and the Radio 2 port is connected to the HF transceiver with the multi mode communications capability (you may customize this however). The MFJ1278 suffers from one major deficiency as far as LAN-LINK is concerned. The Echo-As-Sent only works in the AMTOR Communications Mode. That means that you will not see the contents of a file echo in the incoming window as the file is being transmitted in the RTTY mode. The following functions do not work because either the TNC does not support them or does not do so in a consistent manner. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 5 Page 130 Pactor (As of time of release of 2.10) TNC Transmit Buffer flush. The SIGNAL Communications Mode. The AMSAT-OSCAR Menu does not allow UoSAT option. CW Identification. 7.0 Heath HK-21 K3WGF noticed that his Heath HK-21 TNC didn't seem to have the proper circuitry to support true DCD on pin 8 of the RS232 connector. Even though the pin was labeled DCD it didn't signal properly. Set the DCD function in LAN-LINK to OFF to make the Capture-to-Disk close out normally rather than continue to remain engaged. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 6 Page 131 Appendix 6 Anomalies and Bugs This section discusses various anomalies and bugs. 1.0 Command/Converse Mode Anomalies Since the Program has no way to check the command/converse mode status of the TNC, you may see various "Cmd:" and other "error messages" from the TNC when using the menus or function key commands. Ignore them for now. If you get an error message, try using the function key again. 2.0 Buffer Messages in AMTOR Beacon CQ Mode In the AMTOR Beacon CQ Mode, if the other station drops the link while you are recording the text, BEFORE the callsign has been recognized as a valid callsign, LAN-LINK will time out before logging the QSO and restart the CQ sequence. If someone else calls in before the time-out has occurred, the text from both stations should be captured to disk, but the log entry may not show both stations. You should compare the callsigns in the logbook with the "RUN" file for QSO purposes. LAN-LINK in the Beacon/Mailbox Mode, normally logs the contact at the end of the line in which it recognized the callsign as a valid callsign. 3.0 FEC +? Responses in AMTOR Beacon CQ Mode In the AMTOR Beacon CQ or Mailbox mode, if another station sends a +? in the FEC Mode, the beacon will attempt to send the LAN- LINK.TXT file. The PK-232 however is not in the Converse Mode at that time and will interpret the text of the file as commands. If by some chance, the text corresponds to a valid command the PK- 232 will execute it and put the PK-232 in an unknown state and you may not notice that it did. As such I recommend that the first character of each line in the file LAN-LINK.TXT be a non valid command character such as a number or a period (.) or another punctuation sign. 4.0 Using a Monochrome Monitor If you are using a monochrome monitor, the text you type into the Outwindow may be fainter than the incoming text. This is because of the default colors used. Change the colors using the Parameter Menu. 5.0 The Packet Conference Mode The Conference Mode has been tested on a PK-232, KAM, a SANYO LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 6 Page 132 MBC-675 which has a clock speed of 4.7MHz and other PC clones with faster clock speeds. If you have problems with intermittent selection of I/O channels try slowing down your CPU clock. There is a software delay loop in the program that is used to allow the TNC time to switch I/O streams after receipt of the stream change command. This delay is there because LAN-LINK tests for a connect on each channel before outputting any text, so that it does not send un-addressed packets on non connected I/O channels. 6.0 Packet Conference Mode Disconnects Any Packet conference Mode disconnect returns the TNC to the Command Mode, even if you remain connected to other stations. 7.0 Strange Events If the TNC does not use an interrupt driven serial port you may experience problems when using baud rates greater than 1200. The PK-232 DOES NOT LIKE LAN-LINK to use RS-232 baud rates faster than 2400, and sometimes not even that. Use 1200 until YOU have tested and ARE SURE that a faster one will work. If you have any strange problems and are using an RS-232 terminal baud rate between the PC and the TNC which is greater than 1200, set the Terminal Baud Rate to 1200 and see if the problem goes away. Make sure that your configuration is set the way you think it is. Verify it using the Parameter Menu. You must have at least one common call or scan word in your SYS file, or you will get errors when you update the SYS file. 8.0 *** DISCONNECTED In the Packet Communications Mode, when you are connected to someone and the TNC sends "*** DISCONNECTED" to the computer, LAN-LINK thinks you have been disconnected and resets. This normally only happens when a true disconnect occurs. However, if the text shows up in the middle of a line being sent to you, it will have the same effect. LAN-LINK will think that you have disconnected if the DCD Flag is not set in the SYS file, and the TNC does not use the DCD signal on pin 8 of the RS-232 interface. 9.0 *** CONNECTED In the Packet Communications Mode, if you are monitoring traffic on the LAN and someone sends a packet containing "*** CONNECTED", LAN-LINK thinks you have been connected, if the DCD-Flag is not set, and the TNC does not use the DCD signal on pin 8 of the RS- LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 6 Page 133 232 interface. 10.0 Greek Characters and Other Garbage in the Incoming Screen If you see Greek characters in the Incoming screen you probably have the wrong parity set in the TNC. First make sure that the RS-232 baud rate is correct. If it is, take the batteries out of it and reset it. If that fails, play with the parity. LAN-LINK sets the serial port as configured in the TNC.SYS file for each TNC. For example, for the PK-232 it is 8 bits, no parity. For the TNC2, it is 7 bits. If you still can't get LAN-LINK to talk to the TNC, set the interface to 7 bits in the configuration file. 11.0 Dumb TNC If the TNC seems to respond to commands but is not sending anything back, you may have one of two problems. You may have a bad RS-232 cable with a wire disconnected. If the computer can operate the TNC in another communications program, try to reset the TNC, take the batteries out, etc. You may also have a not-so- compatible PC. 12.0 Intermittent Lockup Watch out for flow control problems on the cable between the TNC and the PC and between the PC and the Display. Versions of LAN.LINK up to and including 1.55 used software handshaking. Anytime the program received a Control-S (^S) character from the TNC it waited until it subsequently received a Control-Q (^Q). These characters can appear on the LAN in a binary packet, either when binary file transfers are in progress, or in a Inter NET/ROM message. To avoid this lockup, a line containing "MFILTER 19" was added in the LAN-LINK.SYS file for the PK-232 to make the TNC filter the ^S character out and not pass it to LAN.LINK. LAN-LINK 1.56 and onward use hardware hand- shaking so this problem should not appear. However if the FLOW and XFLOW parameters are not set to OFF in your TNC, LAN- LINK can appear to lockup. Make sure that they are both set OFF in your TNC. 13.0 Automatic Functions Don't Work This usually happens with the KAM. Set the DCD Flag off, and the automatic functions should work. Note that in this case the multi-connect functions will not work. 14.0 BBS Zap Failure If the BBS Zap hangs up in the middle of sending a message, the LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 6 Page 134 probability is that the LAN-LINK is waiting for the PBBS to send it a word it recognizes. You have probably not configured the "PBBS Read Subject" and "PBBS Message" Strings (lines 43 and 44) in the LAN-LINK.SYS File (See Appendix 2, Section 18.18). 15.0 LAN-LINK Forgets the Band/Power Information LAN-LINK picks up the band and power information from the logbook. You can set them via the "0" option in the Parameters Menu. If the logbook is empty, LAN-LINK will not remember the settings when it is switched off. Put at least one entry in each logbook. 16.0 Zmodem Binary Transfer Problems Some stations perform binary transfers with no problems, others seem to have problems. If you are having problems with the binary file transfers make sure: * You have enough memory left over after loading LAN-LINK to run the external communications protocol. * The QZ*.BAT files have the correct port and baud rate values. * The TNC is set for 8 bit transfers. * Both stations are using the same data rate between the PC and the TNC. * The TNC does not filter any characters out of the data stream, i.e. MFILTER or the equivalent parameter in your TNC is not set. * Make sure you try the binary transfers via the LAN-LINK menu. * Read the PCZ Documentation file and set the Environmental variables correctly. * If all else fails, try a different external protocol. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 7 Page 135 Appendix 7 Updates, Revision History If you are updating from a previous version of LAN-LINK, the following changes were made in recent versions of LAN-LINK. 1.59 F10, First menu character, RTTY/CW file transfer and QBU transparent mode bugs fixed. QTA ack, left/right arrows in log prompt, Local time display, QZU/QZD Zmodem, Metabeacon in packet, MCON control in SAREX Mode, L option in Edit menu, ! in Call menu, K and N in Log Menu, and Z in SAREX Menu added. B removed from call menu. Alt-Y now does RY's in RTTY. XMITOK ON/OFF toggle in PK-232 CW mode. Scrollback not written to capture file. 2.00 ELMER, Alt-W, word wrap, G option in Edit menu, Strswitch chars & error_st in sys file, added. KAM cw/cmd bug fixed, AMTOR sets narrow shift, connect timeout configurable, KAM RX/TX inv added, bell filtered out of connectee/log call, KAM cw and other parameter changes, log power/band picked up from log, custom word[20] in prompt, Elmer added, event timer 2/6 reset change, MH fire delay for KAM, ^T filtered out in all tncs, #T in contest text, NAVTEX and navy MARS enabled for KAM/MFJ1278, flag_XMITOK added, base count added to SYS file, CTEXT saved. 2.10 PACTOR (KAM, PK-232) added. Converted to TP6, Bug fixes Init: 7/8bits, log package changed, Elmer.qso loaded at start-up, Elmer RUN commmand, BBS custom commands, Flag_Inhibit_Logging, Logging package, FLAG_Printer_Perm, TNC_parameter, mode at start up, QIC, QMH in menu, QTR, LAN-LINK.OUT, ANSI Colors, PacketCluster Log Search mode added. ELMER resets on disconnect, MFJ1278 radio port customzable, Shut down flag 5 deleted, BBS upload states changed. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 136 Appendix 8 ELMER An Expert System Based on a Finite State Machine There are two versions of ELMER supplied with LAN-LINK. One is built in for use in packet mode communications, when connected to someone else. The second version is a stand alone version for use in developing the text files and the logic. The stand alone version lets you program and debug your own personal ELMER on your own. The stand alone version is a separate product and requires separate registration. Most initial amateur radio contacts (QSO) are somewhat repetitive, in that they send the same information each time. In digital mode communications hams don't type exactly the same information in every QSO, but in general the information exchanged is a subset of a standard set. Hams have noticed this phenomenon and have each created and used files containing standard information. This fact was noticed years ago, and the first so called "brag tapes" were invented to serve that need back when they were using teletypewriters and generated paper tapes for the standard information. ELMER takes that concept a little further and provides expert system. By parsing the incoming text, ELMER will recognize certain words and transmit text files containing replies or further questions, just as if the operator was at the keyboard. Hams can use this feature to build a smart server they can put on-line on the LAN. The server will prompt people and will serve an educational purpose. ELMER can be set up to teach people about packet radio, license upgrades, or anything else. ELMER can also be programmed to recognize different languages and hold a conversation in those languages. In fact, apart from the dedicated educational and informational server applications, ELMER may be configured with such a variety of vocabulary files so as to pass the Turing test in most typical amateur radio digital mode conversations. 1.0 INTRODUCTION ELMER is a program which allows you to build an expert system. It uses the ELMER.QSO file to set up the state machine. The ELMER contains an array of words to be matched, current states, next states, and files to be loaded. The ELMER starts up in an initial state. When a line of text is received, it begins to match an array of words against the incoming line of text. It starts matching the words in the order that they are present in the array. It only matches words that are enabled for the current state or for state 0. If it finds a LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 137 match, it advances the next state, and if a valid file name is present (and exists), will output that file. The ELMER will then continue scanning the line of text from the point that the last match was obtained. At the end of the line, it waits for the next line. 1.1 Expert Systems Before discussing ELMER, here's some information about expert systems. An expert system contains knowledge about a particular field to assist human experts or provide information to people who do not have access to an expert in the particular field. It is an information system that can pose and answer questions relating to information borrowed from human experts and stored in the system's knowledge base. Although they vary in design, most expert systems have a user interface, a knowledge base, and an inference engine. 1.2 The User Interface The User Interface to the expert system is the way that the user interacts with the system to extract information from the system. 1.3 The Knowledge Base The Knowledge Base of an expert system contains both declarative and procedural knowledge. The facts describing the situations, events and objects are called declarative knowledge. Procedural knowledge is the information about courses of action and the rules governing the actions. There are various kinds of rules that may be employed. 1.4 The Inference Engine The Inference Engine controls how and when the information in the knowledge base is applied. It determines how the rules in the knowledge base are to be applied to the problem. 1.5 Features of an Expert System The following list of features are desirable in any expert system. 1.5.1 Useful The system should meet a specific need. 1.5.2 Usable The system should function so that even a novice computer user LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 138 finds it simple to use. It should be able to respond to simple questions. 1.5.3 Educational The system should allow non experts to increase their expertise. In a similar vein, the system should be able to explain the reasoning behind its advice to allow the user to determine the validity of the advice. 1.5.4 Adaptable The system should be able to learn new knowledge. 1.6 Using an Expert System Expert systems take the form of software packages residing on a hardware platform (computer). The most common use of an expert system is via a man-machine dialogue. The user types something at the keyboard and the system replies. The user interface accepts the input. The input is parsed in some manner. The inference and knowledge engines process the user input in a predetermined manner and an output appears. The parsing function may be a simple pattern matching method commonly called keyword analysis, or a more complicated function using syntactic analysis. Keyword analysis is a logical function in which the presence of various keywords are detected. When a keyword is found, the system responds in the manner in which it has been programmed. For example, if the system detects the words "the wx" in a question, it may respond with " the wx here is sunny". In syntactic analysis, a sentence is analyzed according rules which allow the system to respond differently to keywords which appear in different sequences. For example, the system may respond differently to the question "what is the wx" and "the wx" if it recognizes those words in a sentence. 1.7 The Semantic Network The most general and oldest artificial intelligence scheme for representing knowledge is the semantic network. A semantic network is a collection of objects called nodes. The nodes are connected together by links. Ordinarily, both the links and the nodes are labeled. A drawing of a semantic network contains bubbles to represent the nodes, and lines connecting the nodes to represent the links. Both nodes and links are labeled. The drawing looks just like a PERT or CP/M chart. It is also the drawing used to represent a state machine. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 139 1.8 A State Machine A state machine is a system that exists in several states. The system makes a transition from one state to another as a result of a stimulus. All states and transitions are defined at the time the system is designed. The links in the semantic network are the transitions in the state diagram. 1.9 The User Perception The user perception of an expert system is that the system appears to be in a rest state. It receives an input from the user and enters a transition to a state in which it processes the data it has just received. After processing the input, it generates an output and returns to what seems to be the same rest state. In reality, the two rest states (initial and final) are different. 1.10 ELMER ELMER is an expert system for amateur radio. ELMER is based on a finite state machine using table driven software. The declarative knowledge is stored in the form of separate ASCII text and command files. The procedural knowledge is stored in the state table. The Data files in ELMER correspond to the Knowledge Engine (and the Inference Engine). The State Tables correspond to the Inference Engine. ELMER also contains an ASCII editor for text files, and a tool to view the state table. These tools allow the user to "teach" ELMER new knowledge. 1.11 Responses to an Input ELMER has three kinds of reaction to a word match. It can do nothing, output a test file, run a command or overlay a new state table. ELMER's state table contains four entries:- 1.11.1 Current State This is the state that the string match is performed in. ELMER can have up to 63 different states. 1.11.2 Next State This is the state that the ELMER will advance to if a string match is found. 1.11.3 Repeat Flag This is a flag to allow or disallow repeats. If it is a 0 repeats are allowed. If it is a 1, they are not. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 140 1.11.4 Command Flag This is a flag to tell the ELMER how to treat the file. If it is a 0, load a text file; a 2, overlay the current state table with the defined one. 1.11.5 Keyword This is the text string to match in the syntactic analysis of the input text. The text string can be up to 15 characters long and can include spaces. The match is case insensitive, i.e. there is no difference between upper and lower case. 1.11.6 Data File This is a text file to be loaded or a new configuration file. 1.12 Syntactic Analysis ELMER performs syntactic analysis on the input text in the manner described below. ELMER performs a string match on the line of received text against each keyword entry in the state table. ELMER starts with the first entry. If a match is made, ELMER changes state and performs the transient function defined by the Command Flag. All words in the input text including the keyword are then deleted. ELMER then continues the string match until either the input line of text has been reduced to zero length, or, the line of input text has been tested against all keywords in the state table. 1.13 Programming ELMER Programming ELMER is simple. The knowledge base is broken out in terms of states and transitions. States can be passive or active. A passive state is one in which ELMER does nothing other than accept/parse further input. An active state is one in which ELMER loads and displays a text file containing information or shells to DOS and runs an external program. ELMER contains a set of tools for programming and debugging purposes. A state table for the procedural knowledge is drawn up using pencil and paper and a large sheet of graph paper. The built in text editor is then used to enter information into the table. The individual text files containing the knowledge are also created using the editor. The state table viewing tool is used to check the entries. The state table loading capability is used to exercise ELMER and verify the logic. Because the procedural knowledge is contained in the state table, all sorts of rules and linkages may be used. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 141 2.0 The State Table (ELMER.QSO) File These are the contents of the ELMER.QSO file. 2.1 The Directory Path to the ELMER Text Files This item is the directory path to the sub-directory containing the ELMER text files. For example "c:\LAN-LINK\ELMER\" or "c:\ELMER\" or just "c:", if you put them in the same sub-d- irectory as ELMER.EXE. If you do use a path you MUST have the last "\" character at the end of the sub-directory name because the program concatenates the directory path to the ELMER. 2.2 The Start Up File This line is not used in LAN-LINK's ELMER. It is only used in the stand alone version. It contains the name of the text file to output the first time ELMER is invoked (if present); 2.3 Window Colors These seven lines are only used in the stand alone version. They are the numbers which correspond to the colors of the seven different windows displayed on the screen of the stand alone version, in the following order. 2.3.1 Status Window Color The color of the window at the top of the screen. 2.3.2 OutWindow Color The color of the window in which the replies are displayed. 2.3.3 InWindow Color The color of the window in which your keystrokes are displayed. 2.3.4 BottomWindow Color The color of the bottom line of the screen. 2.3.5 Promptwindow Color The color of the window in which menus are displayed. 2.3.6 Option Color The color of the highlighted characters in the menus and prompts. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 142 2.3.7 Alarmwindow Color The color of the window in which error and alarm messages are displayed. 2.4 The ELMER Initial State This item is included to allow you to have different state machines, each starting with a different state number. 2.5 State Machine Parameters The next few lines contain the state machine parameters. 2.5.1 Current State This is the state the string match is performed in. LAN-LINK allows up to 63. 2.5.2 Next State This is the state that the ELMER will advance to if a string match is found. 2.5.3 Repeat Flag This is a flag to allow or disallow repeats. "0" means that repeats are allowed. "1" means they are not. 2.5.4 Command Flag This is a flag to tell the ELMER how to treat the file as shown below. Flag Operation 0 Load/display a text file. 1 Execute a BAT, COM, or EXE file. 2 Overlay the current state table with the new one. 2.5.5 Keyword This is the text string to match. It can be up to 15 characters long and can include spaces. The match is case insensitive, i.e. there is no difference between upper and lower case. 2.5.6 Data File This is either a text file to be loaded or a command file to be executed, depending on the state of the Command File Flag. An "*" character defines a "do nothing" state in which the Data File is LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 143 ignored. The two character sequence "#1" will cause ELMER to clear the screen before displaying the rest of the text in the data file. 2.6 The State Machine File An example of some state machine parameters is shown in this typical extract from an ELMER.QSO file. 1, 2,0,0,what,* 2, 3,0,0,englishman,* 3, 4,0,0,doing,* 4, 1,0,0,country,me-usa.txt 1, 1,1,0,equipment,pk232com.txt 1, 1,0,0,wx,localwx.txt 1, 5,0,0,kenwood,kenwood.txt 5, 1,0,0,811,811.txt 1, 1,0,0,hello,hello.txt 0, 1,0,0,name,joe.txt An "*" character defines a "do nothing" state in which the Data File is ignored. 2.7 Example of Programming the State Table Consider a typical question that I get asked. "what's an englishman like you doing in this country ?" followed by " The equipment here is ....." Assuming that the ELMER is in State 1, and that the first few lines in the ELMER.QSO file are as shown above. The ELMER recognizes the word "what" and advances to State 2. Since the file name is an "*" character no file is sent. The ELMER then recognizes the word "englishman" and advances to state 3. The ELMER machine then recognizes the word "doing" and advances to State 4. The ELMER then recognizes the word "country" advances to State 1 and transmits the text file "me-usa.txt", because the Command Flag is a 0. It then recognizes the word "equipment", remains in State 1 and transmits my brag tape file called pk232com.txt. Since the Repeat Flag is a 1, the ELMER will not retransmit pk232com.txt should it once again recognize the word equipment while in State 1. Since the ELMER scans sections of the line, the same effect will be achieved if the incoming text had looked like :- LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 144 "what's an englishman like you doing in this country ? The equipment here is ....." You can only have 63 lines in any one state machine array. You can define up to 64,000 different states. Each state must be an integer. State 0 is a wild card state. This means that any word in the array coded for state 0 will be matched against the incoming text whichever state the machine is in. The entries in the state machine file must end with a line that contains state 666. For example 666, end of file The number of lines in the array and the current state at the end of each line scanned are shown in the status window. 3.0 The Stand Alone Version Status Window The Status Window provides you with some diagnostic information about the state machine. C: shows the current state. T: shows the number of states (lines) in the state table. ELMER.QSO represents the name of the current state machine. 4.0 The Stand Alone Menu You bring up the menu by touching the "Escape" character. You are then presented with the options shown in Figure 8-4. To activate an option touch the highlighted key. Figure 8-4 ELMER Menu E Edit Any File L Load ELMER.QSO P Pick File to edit S Edit ELMER.QSO X eXit to DOS * Show State Table 4.1 Edit Any File This option allows you to edit text files using the LAN-LINK compatible text editor. 4.2 Load State Table (ELMER.QSO) This option allows you to reload the state table, or load a LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 8 Page 145 different one. If a different state table is loaded, its name will appear in the menu. 4.3 Pick File to Edit This option allows you to pick a file with the default filetype of "TXT", and edit it. 4.4 Edit State Table (ELMER.QSO) This option allows you to edit the state table (configuration) file. 4.5 eXit to DOS This option allows you to exit to DOS. 4.6 Show State Table This option allows you to see the contents of the state machine. It is used in debugging the logic to ensure that the contents of the table match what you thought you put in. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 146 Appendix 9 PCZ Binary file Transfers LAN-LINK uses the PCZ public domain external protocol for binary file transfers by shelling to DOS and executing the QZ*.BAT batch files. The QZ*.BAT files are set up for you by the INSTALL program. This appendix contains the documentation for PCZ as supplied by the developers of PCZ, in case you have problems making binary file transfers work in your system. PCZ - A Public Domain implementation Zmodem, Ymodem, Xmodem, Xmodem-1K, Sealink for the IBM PC family PcConnect Zmodem by Drue Kennon and Gary Smith PCZ is a public domain Zmodem implementation that will allow users of communication software that does not implement internal Zmodem to access it through an external program. It is a full- featured version of Zmodem, but does not have the large volume of bells, whistles & options provided by Omen Tech's DSZ. However, I do believe that it will be suitable for the average demanding BBS'r. PCZ provides support for the basic Xmodem variants: Xmodem, Xmodem-1K, Ymodem & SEAlink. The following is a description of how to start PCZ for file transfers. LEGEND Data enclosed in "[" "]" are optional. Data enclosed in "<" ">" are required. Send Command line: PCZ <1-8> <300-19200> [m] [f] [d] [s] <s?> [r] [@]<filespec> Recv Command line: PCZ <[1-8]> <[300-19200]> [m] [f] [k] [d] [s] <r?> [r] [filespec] Ref: 1-8 - the number 1 - 4, -(8) << PS/2 >> 300-19200 - the number 300, 1200, 2400 etc... m - front-end menu option (see MENU) f - enable FOSSIL comm driver routines k - rx keep aborted received files d - disable video memory writes (use dos) s - request enable Super_Z transfer mode (zmodem only) r?,s? - transfer type sz, rz, sx, rx etc... LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 147 r - resume/recover aborted transfer (zmodem only) @ - command file transfer alert flag (SEAlink, Z,Ymodem) filespec - file name w/extension {complete file spec allowed} {drive:\path\filename.ext} Flags should be placed as shown for standardization purposes. i.e. "f" before "d"; "d" before "k"; "rz,sz" before "r" etc... Due to the nature of the beast, no support is provided for a default port & no default port speed is assumed. NOTE * See environment variables below for more on default port/speed I personally never enter "port" or "speed", but always enter their values. i.e. pcz 1 9600 f sz xxxxxxx.xxx The batch files included reflect this method. "ZMODEM RECEIVE" << SINGLE >> PCZ 1 9600 rz myfile.ext - assume your specified file name. << BATCH >> PCZ 1 2400 rz - Receive ALL sender files. PCZ f d k rz r - Receive ALL sender files assume PCZPORT & PCZSPEED values use FOSSIL routines use standard DOS screen output KEEP all aborted files. RESUME any incomplete previous files. one file mode: PCZ 1 9600 rz INFILE.ARC - Receives one file and names it INFILE.ARC PCZ 1 9600 rz r INFILE.ARC - Recovery effort on file INFILE.ARC NOTE * A word about command line switches might be in order here. The switch flags " f, d, k " are global. That is they control PCZ and not any particular protocol. The "r & s" switch is isolated within zmodem, but is applied to both sender and receiver. If you want PCZ's resume code enabled when sending a file then the sender must specify "r" on the command line. Accordingly if the receiver requests resumption of an aborted transfer, the sender must have "r" specified or we won't resume anything. This was requested by BBS Sysops who track download bytes, transfer points etc... Probably so you aren't charged twice or the such like. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 148 "ZMODEM SEND" << SINGLE >> PCZ 1 9600 sz OUTFILE.ARC - Send one file to receiver. << BATCH >> Create a TEXT command file with one complete file spec per line, which includes drive and directory information for each file that is not in the directory PCZ was called from. e.g. C:\MYDIR\THISFILE.ZIP There is NO limit to the number is allowed. Have no blank lines in the file. Place the "@" symbol as the first character of the filename. Pass it to PCZ on the command line as follows: PCZ 1 2400 sz @OUTFILE.TXT What you name the command file is your business. It simply must be a standard ASCII file with no software or printer control codes present. An alternative to creating the command file for sending 2 or 3 files may be used. Simply type the file names on the dos command line separating each one with a space. Remember the receiver must be set to accept batch uploads or you might be spinning your wheels. Some BBS packages are just now coming on-line with batch upload features using PCZ. They normally indicate (BATCH) if it is supported. BBS << BATCH >> One method for implementing batch uploads on a bbs is to use the log file and examine the transfer status character. The first character of each line in the log file denotes how the transfer finished. A "1" for good transfer & "0" for a failed transfer. Armed with this information, simply setup to call PCZ in batch receive mode. After PCZ has finished and your bbs code has control, open the logfile and read in the line(s) of information. You may now format a string to send the user about the status of each file he/she sent, prompt for a file description etc.. After you have dealt with each entry in the logfile, simply close LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 149 the file and delete it. PCZ will create a new file for the next transfer session. If you desire a continuous record of the transfers then you should create your own and append each entry you read from the pczlog to your continuous log file. The information below shows exact start positions for each piece of data. The x's denote the length of each element, the first (x) shows start position as PCZ will write it to the log. e.g. Below, the file size is 47877. PCZ will always write the file size as a 7 character string which begins at position 21 in the line. Hence, read from pos (21) to pos (27), trim any blanks & convert to decimal value etc.. Log extract w/char positions: 1 2 3 4 5 1234567890123456789012345678901234567890123456789012345 x xx xxxxxxxxxxxx xxxxxxx xxxxxx xxxx x 1 sz PCZ40x.ZIP 47877 @ 2400 bps @ 237 cps 0 6 7 8 6789012345678901234567890 xxxxxxxxxxxxx errors Fri 10/5/1990 "XMODEM VARIANTS" To receive files using any of the Xmodem variants, the format is: PCZ <port> <speed> rs filename - SEAlink receive PCZ <port> <speed> rs - SEAlink Batch receive PCZ <port> <speed> rx filename - Xmodem receive PCZ <port> <speed> r1 filename - Xmodem-1K receive PCZ <port> <speed> ry filename - Ymodem receive PCZ <port> <speed> ry - Ymodem Batch receive Remember the "k" option works for all of the receive modes. Hence you can receive a file via SEAlink, have it abort on errors, and then later RESUME the transfer using Zmodem. To send files using any of the Xmodem variants, the format is: PCZ <port> <speed> sx filename - Xmodem PCZ <port> <speed> s1 filename - Xmodem-1K PCZ <port> <speed> sy filename - Ymodem * PCZ <port> <speed> ss filename - SEAlink * * Refer to Zmodem Batch sending for batch transfers via Ymodem and SEAlink NOTE: The bytes and cps rate reflect the actual number of bytes sent to, or received from the IOBuffer as a transfer progresses. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 150 It does not necessarily reflect any specific "BLOCKSIZE". When sending, as a transfer nears it's end, you will see the cps decline. That's because PCZ uses buffered output vs a simple "sector size" buffer. This will let you see actually how PCZ is progressing in the transmission of data. In the best case "Full Streaming Zmodem", you will see the time for actual file data; worse case time will reflect the transmission of data headers and block acks. It is different, but I hope everyone can appreciate a more accurate account of what is happening inside the powerful zmodem protocol. ** : The "Transfer Time" reflects PORT speed, (NOT MODEM) speed! If speed conversion is being used, FORGET the transfer time. "ENVIRONMENT VARIABLES" PCZ supports several environment variables which can make setting up a comm pkg. or BBS more "user friendly". These variables are as follows and should be placed in the autoexec.bat file as I have them shown here or modify the setenv.bat file included to accommodate your system. "DRIVE" refers to the letters "A".."Z" "YOURDIR" refers to a complete directory specification. i.e. \COMM\ARC\ "YOUR.FIL" refers to a filename with extension that you want PCZ to use vs it's default name. "DIRRX" set DIRRX=drive:\yourdir\ This variable provides the ability for all your received files to be placed in a single location. It is very useful for bbs purposes as well as general comm program usage. If you specify a directory spec on the command line, it will override DIRRX. Therefore you can easily set the variable and then just forget about it. If DIRRX isn't set and no spec. is given on the command line, your receive file will be created in the current active dos directory. "PCZLOG" set PCZLOG=DRIVE:\YOURDIR\ In the log file's case, it specifies the directory you want your PCZ.LOG file to be kept in. If "PCZLOG" is not found in the environment then no log file is generated. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 151 set PCZLOG=DRIVE:\YOURDIR\YOUR.FIL As an option to the log file name "PCZ.LOG" you may specify your own filename in the filespec. This provides greater flexibility with some bbs packages such as RBBS which expects it's own naming convention to be used, and for multitasking environments etc... If your "YOUR.FIL" exist, it overrides filename "PCZ.LOG" in all cases. "PCZPORT" set PCZPORT=(1-8) PCZ will use the port number (1-8) as the default port. "PCZSPEED" set PCZSPEED=(300-19200) PCZ will use the speed (300-19200) as the default speed. NOTE ** If you specify the PORT or SPEED on the command line, it will override a default set by the environment variables. "PCZDIR" set PCZDIR=DRIVE:\YOURDIR\ If you experience any problems with PCZ not being able to access it's overlay file, setting this variable will cure the problem. DRIVE:\YOURDIR\ should point to the directory where you have located PCZ.EXE IMPORTANT NOTE: NO SPACES are allowed when setting an environment variable! i.e. {WRONG} set PCZLOG = C:\COMM\ will not work. That's not my fault. It is just DOS.... i.e. {ahhhh} set PCZLOG=C:\COMM\ "PORT & IRQ" It has seemingly become necessary, instead of interrupt sharing, to reassign Comm. PORT addresses and use seldom triggered IRQ lines e.g. "5 & 7" to allow multiple "more than two" ports on one machine. Efforts to support this trend have been successful with PCZ. Referring back to our PCZPORT environment variable: LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 152 set PCZPORT=1 If you have reassigned your IO card addresses etc..., you can force PCZ to comply with your wishes. Lets say you want to use PORT 3 @ 2E8h on irq 5. You set PCZPORT in this manner. set PCZPORT=3,2E8,5 | | | | | |____ IRQ line number | |_______ PORT address |__________ PORT number If you specify an invalid address or one your card isn't set for, then PCZ will simply abort during it's port validation routine. This method should provide the support needed for those who like to match their wits against the cpu's. "Super_Z" (tm) Always in search for faster from fast. Super_Z takes zmodem to the ragged edge! If you are one of the blessed, and enjoy relatively noise free transmission lines, you should see an increase of 2 to 3 % efficiency. XON/XOFF MUST be disabled and the modem must pass these characters. You may activate Super_Z via the command line switch "s". As is usually the case, Super_Z can be called by the receiver or by the sender. That is to say, that either can flag for Super_Z and if the remote version supports Super_Z, we're doing it. Regarding noise, a seldom thought of fact is that just because your local transmission lines are great to one place, someone else's local lines may be the pits. A good example is.... When I log on to the "Corner" from Texas on a "596" extension I rarely ever get a line hit. When I use the "995" extensions I am prone to hits anytime. A reverse situation might occur in your particular area. It simply depends on the quality of any of the many exchanges you might encounter. I can only hope you are one of the lucky ones. "NETWORK SUPPORT" PCZ has been tested completely in a network environment. It will allow multiple users to read the same file via use of DOS's shareable attribute. It will also lock any files that it is currently writing to. This has been tested using Novell Netware, LAN Manager, and CBIS Network-OS. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 153 "MENU FRONTEND" Many fine programs exist which allow protocol engines to be called from a communications package. In an effort to make PCZ all the more user friendly, there is now a simple menu system built into the program. It is controlled by the file PCZ.CFG which is included in this zip file. Take a few moments to read over it. It may be that it is just what you are looking for in the way of a nice user interface. The design and layout of the system is very simple and straight forward. You control the options and protocols you wish to have active. PCZ.CFG comments explain the various functions you can use. To use the menu system simply call PCZ in the following manner. PCZ m Make your menu selections and complete the command line with your filespecs. "FOSSIL SUPPORT" FOSSIL is an acronym for "Fido/Opus/SEAdog Standard Interface Layer". This version of PCZ implements the use of FOSSIL communications support. To date only one, "X00.SYS" driver has been tested to work with PCZ. X00.SYS is a product of Raymond Gwinn. It has proven itself in many environments and I recommend it to you without reservation. X00.SYS was chosen because it provides "FIFO" etc... support for the 16550 UART chip. My internal routines support the chip but not all it's features. Also X00.SYS provides enhanced ability to work in a multitasking environment such as DeskView. If DeskView is active PCZ gives idle processor time back to the cpu for smoother operations. For a brief description of setting up X00.SYS on your system read the enclosed file PCZFOSSL.DOC Making use of the driver with PCZ is as simple as adding "f" to the command line. It should be placed after the baudrate in all transfer types. i.e. PCZ 1 9600 f sz OUTFILE.ZIP When PCZ starts, it will check for the presence of the driver in memory. If it is resident all will proceed as planned. If however, the driver is not in memory, PCZ will gracefully shut down with a message stating this fact. I gave careful thought to jumping to the internal routines, but decided against it for a couple of reasons. In some cases the ports may be scrambled which will surely cause a system lockup on PCZ's part. A problem may exist with the driver you are using, giving false info which PCZ's routines would not like very much. A "dumb" terminal might LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 154 have charge of things and not want another routine hanging around, etc... "PHONE SUPPORT" Phone support can be provided when you require it, if you call while I am home. I umpire for our local women's softball league on Mon. & Tues. nights. I play golf on Wed. & Thurs. evenings. Fri. night I do what Maureen tells me to do! Sat. is up for grabs and Sun. morn & evenings I am in church. Please try me sometime other than those mentioned ...... Seriously though, any night (late) will be fine. Just try and make it before 10p.m. CST if possible. Note from the author: Over the last year PCZ has received some very good reviews. More users rely on the program for their transfers now than I thought would ever be interested. For this I am especially grateful and would thank each one if possible. Gary & I will continue to grow with the needs of the BBS community. We ask for your continued input and support, with our assurance that your IDEAS, "cheers & jeers" are taken with sincerity. Thanks Drue History ------- V1.01.88 - Initial release, no known bugs. Please report any problems to Drue Kennon. V2.01.89 - Extended version that contains Xmodem, Xmodem-1K, Sealink, and Ymodem Batch in addition to Zmodem. Also provides full file sharing for use in networking environments. V2.11.89 - Fixed several reported bugs. Enabled hardware flow control for use with MNP type modems. Enhanced port speeds up to 19.2k, and tightened some code for more efficient operation. Properly set errorlevel 1 in event of transfer failure. V3.03.90 - Fixed a problem with SEAlink xfers not seeing the last EOT. Batch sending for SEAlink per request. Enhanced some screen data writes. V3.06.90 - Fixed a problem with SEAlink xfers created by making the last fix. Zmodem command file name can't be fouled due to misunderstanding the docs. NOTE: LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 155 Unless forced into it by the users, I do not plan to support 7 bit data transfers. Nor can I figure why any IBM machined BBS would? Did I miss something along the way? V3.08.90 - Got with the program and added support for FOSSIL driver. e.g. Gwinn's Communications Controller, X00.SYS add "f" to cmd line params for fossil). Removed internal support for default port and speed which caused problems for multitaskers. Defaults are now specified through environment variables. Added environment variable for default receive dir. Reinstated environ- ment variable for pcz log file. V3.09.90 - By popular demand, namely "Gary", I added yet another multitasker enhancement. Since the cpu is much faster than the port, idle time occurs during output. This time is now "given back" to the cpu, allowing the "other side" to operate smoother and more efficiently. V3.10.90 - Some users mentioned that PCZ would wait forever in a transfer if the carrier was lost. I couldn't dupe the problem, but added several more checks nonetheless. The logfile has changed so that you may specify a full filespec. including filename for you logfile in the env. var. The first char of each line in the file represents pass or fail. "0" = failed xfer "1" = good xfer. Keep those cards and letters coming! V3.11.90 - ArrrrG! %#^^#%%@#*$(%*#$%($$%&*( the &*&^*&^ woes of changes really &#$^& my &(&^#$. V3.12.90 - Forget 3.11.90 ever existed! Several routines got a face lift! You should see more efficiency with this release. I can't begin to go through the entire chase with you here, but I need a new can of RAID! Seems there is never a total end with a bug problem, in programming as well as the home! I must offer a special word of thanks to Dick Melville from San Marino for his the help with RBBS interface problems. Dick was an excellent BETA Buster! And to Steve Clancy who finally helped me see there was NO carrier on the line! V4.00.90 - {BETA} Version 4.00 represents a major revision change to PCZ. As you have noticed, if you've used prior versions, there are two PCZ files now instead of one. PCZ.EXE is the global executable file and PCZ.OVR contains the actual protocol functions. The decision to go with overlay functions was made due to the fact that more Sysops are using PCZ with their BBS's in a multitasking environment. Memory usage has been drastically reduced. Additionally, each transfer type function i.e. "sz,sx(1),ss,sy" & "rz,rx(1),rs,ry" is totally self contained which simply means once the program loads and a transfer type is called, no other overlay read is needed. The LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 156 function completes and exits. Simply put; execution time has been enhanced. V4.01.90 - {BETA} Dick & Steve V4.02.90 - {BETA} Dick & Steve V4.03.90 - {BETA} PcConnect, Dick & Steve V4.04.90 - {BETA} PcConnect V4.05.90 - Major revision V4.xx.90 released on the world! V4.06.90 - Some enhancements added here include; Super_Z (tm) by PC², offers enhanced transfer times when used with error correcting modems and relatively noise free transmission lines. No limit to the number of files allowed in a batch transfer command file. Non-standard PORT, IRQ line assignments supported via environment setup. Frontend menu system for comm package use. PCZ is supplied as a ".EXE" file which when executed breaks it's code out into overlays. The largest executable code segment will run well inside of a 64k memory segment. Personal contact may be made by one of the following methods. Drue Kennon Gary J. Smith Rural Route #2 Box 54 6122 Cedar Wood Drive Center, TX. 75935 Columbia, MD 21044 Voice 409-598-3809 The Programmer's Corner Home of "PcConnect" & "PCZ" Data/BBS: 301-596-1180 Data/BBS: 301-995-3744 Data/BBS: 301-621-4636 10 roll over lines in place with over 1.5 gigabytes of storage space DSZ, ZCOMM, Professional-YAM are Copyrights of Omen Technology Inc, all rights reserved. X00.SYS Copyright (c) by Raymond L. Gwinn, All Rights Reserved. PCZ Copyright (c) by Drue Kennon, All Rights Reserved. Super_Z(tm) is a trademark of PC² ** If you are the author of a communications package that has zmodem implemented internally and would like to enable Super_Z in you program for PCZ compatibility, look over SuperZ.Doc. If you have any questions or problems then just drop me a line or call and we will be glad to help you out. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 157 The PCZ Menu Transfer System This is the PCZ.CFG file. ;To make use of this transfer menu system PCZ should be called in the following manner. ;PCZ m <ENTER> ;We assume in this config file that you are using SETENV.BAT to preset your PCZ parameters for PORT and SPEED. If this isn't the case then simply add them on the protocol lines below in their proper place. You should be able to see from the listings the format used here. i.e. ;SEND without the ";" begins send protocol block ;END without the ";" end the protocol block ;The protocol goes on a line followed by the ":" char followed by PCZ's command line options for that protocol. You will be prompted to complete the command line with your filespec(s) once the program is started etc... pretty simple huh? ;Simple yes! but simple minded as well, and if you fail to follow these guidelines.... who knows what type of protocol you might be trying to use for a transfer. Just to satisfy your cats curiosity you may uncomment the first line after SEND. Run PCZ using "m" menu option, select upload and see what happens. No your pc won't bark but it might barf if you select "A" as your protocol type. ;The following represent the send parameters. Using the ";" at the beginning on a line comment out any protocol you do not wish to use during you file transfer sessions. SEND ;flag for beginning of send protocols ;TOSSIT: sp ;This is a curiosity test line ;XMODEM: sx ;send a file using xmodem ;X1K: s1 ;send a file using xmodem 1k blocks ;YMODEM: sy ;send a file using ymodem with file header information ZMODEM: s sz ;send a file using Super_Z zmodem LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 158 SEALINK: ss ;send a file using sealink END ;end of send protocols :The following represent the receive parameters. RECEIVE ;flag for beginning of receive protocols ;XMODEM: rx ;recv a file using xmodem ;X1K: r1 ;recv a file using xmodem 1k blocks ;YMODEM: ry ;recv a file using ymodem with file header information ZMODEM: s rz ;recv a file using Super_Z zmodem SEALINK: rs ;recv a file using sealink END ;end of receive protocols ;You may add any of the other command line switches you wish to the above. They are ; "f" use FOSSIL ; "d" no direct screen writes ; "k" keep all aborted downloads ;Thanks and have fun! LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 10 Page 159 Appendix 10 Other PC Software by Joe Kasser, W3/G3ZCZ 1.0 PC-HAM 3.52 PC-Ham contains the following suite of programs. 1.1 LOGBOOK Full blown logging package. With automatic check of logs for awards such as DXCC. Allows you to recall any entry by call sign within seconds. Indexed displays, QSL'ing, Contest mode QSL'ing (prints the lot) and lots more. Although written in dBASE3 the package contains a compiled version (LOGBOOK.EXE), so you don't need dBASE to run it. The source code is ONLY given to registered users. It can convert your exported LAN-LINK.LOG file to LAN- LINK.DBF to put this package to work. Ideal for DX-peditions or for DX robot users to handle QSLing and log statistics. 1.2 CONTEST Keeps Dupes in memory, logs QSO's to disk in format which can be processed by the LOGBOOK package. Now compiled in Turbo BASIC, source code is supplied so that you can modify the program to meet your requirements. 1.3 CQSS Sweepstakes game compiled in Turbo BASIC. Work the ARRL Sweepstakes contest on your computer. You are located just outside Washington DC. A propagation model is built in to the program. This program is REQUIRED training for all sweepstakes operators. Earlier version of the program is described in detail in Software for Amateur Radio by Joe Kasser G3ZCZ, published by TAB Books, Blue Ridge Summit, PA. 17214. 1.4 WHATSON Predict HF Propagation for given days. Contest mode with printout to whole world at hourly intervals. Needs BASIC. 2.0 STARTREK The Computer Program An ideal task for the beginner to learn a language on, is a simulation game which is written to run on a computer that the beginner has access to. For in that case, there is complete control of all inputs and outputs. This kind of game (in which the player makes decisions based on the information available to him or her available at the time), can be made sufficiently sophisticated and complex so as to make writing it an adequate challenge for anybody. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 10 Page 160 The techniques used in writing a good game are the same that programmers use in professional activities. Writing a good game poses a challenge that allows you to develop good habits and techniques for programming and also allows you to learn a language in an interesting manner. By taking an orderly approach to the game design, complex operations may be clearly understood and converted to computer code with the aid of a language reference manual, irrespective of the language being used. This product teaches the techniques for writing such a game using the STARTREK game as an example, and the BASIC language as the programming language in which to write the code. Registration fees. Single Copy $15.00 10 - 50 Copies $12.00 per registered copy. 50 - 100 Copies $10.00 per registered copy. 100 + Copies $8.00 per registered copy. 3.0 WHATS-UP 1.20 WHATS-UP is a tool for experimenting with orbital dynamics and Telemetry Decoding and display Program for the UoSAT-OSCAR 2, AMSAT-OSCAR 13, Fuji-OSCAR 20 and the AMSAT Microsat Spacecraft (OSCARs 16, 17, 18 and 19). It is table driven via the configuration files to allow maximum flexibility. WHATS-UP contains the following features: Can automatically set Kenwood Radios to spacecraft beacon frequency when satellite comes over your horizon: Can automatically read the frequency from Kenwood Radios to a disk file for Doppler frequency measurements: Can automatically configure a PK-232 for each spacecraft data format: Reads 2 Line and AMSAT format orbit element data files: Provides antenna azimuth and elevation pointing data: Real time, Playback and Dumb Terminal mode: Automatic Capture-to-disk of raw telemetry. Extracts telemetry channel data to a database or spreadsheet readable file for further analysis: Link quality measurement on packet telemetry: Capability to print the raw telemetry as it is received: Up to 16 user configurable display pages (screens): You set the position on the page (width of engineering unit field, and number of decimal places) that a parameter is displayed at: Wild card page (parameter shows up on all pages): Selectable display of Engineering units or raw byte for each display page: Display of raw packets (i.e. STATUS) Color changes if a parameter value changed between successive frames: Audio and visual alarms if a LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 10 Page 161 telemetry value exceeds, falls below or falls outside a preset limit value(s): Dumb split screen terminal mode (in the manner of LAN-LINK): Customizable colors, PC to TNC baud rate, data parity and stop bits: Default spacecraft configuration files: Time of day clock display (in HH:MM:SS format). Real time analysis requires a receiver and demodulator. Analysis of playback data can be performed with just the computer and WHATS-UP. If you would like a copy of WHATS-UP and have captured any telemetry to disk, especially daytime or southern hemisphere passes, please put them on a disk and send it in with your request, a mailer and return postage. Don't let the individual data files become too long. I suggest that you rename them every day in the format YYMMDD.SC, such as 900824.D17, 900824.F20, etc. IF YOU ARE INTERESTED IN OSCAR AND SPACECRAFT TELEMETRY, THEN THIS PROGRAM IS A MUST. 4.0 ELMER 1.00 ELMER is an Expert System Based on a Finite State Machine. There are two versions of ELMER supplied with LAN-LINK. One is built in for use in packet mode communications, when connected to someone else. The second version is a stand alone version for use in developing the text files and the logic. The stand alone version lets you program and debug your own personal ELMER by yourself. The stand alone version is a separate product and requires separate registration. 5.0 BASIC PACKET RADIO Basic Packet Radio explains how the computer can be used to smarten up your use of packet. Not only does the book explain packet radio, it comes with a full feature version of LAN-LINK (for the PC) on disk and contains the manual for the program. The topics covered in the book are outlined below. Getting Started in Packet Radio, What Packet Radio Is, The Shared Radio Channel, The Virtual Channel, The Equipment Needed to Hold a Packet QSO, The TNC, TNC Modes, The Terminal Program. Connecting the PC to the TNC, Command Convention, Making the PC Communicate with the TNC, Determining and Changing the State of a Parameter, Setting the Carriage Returns and Line Feed Display Controls, Flow Control, Connecting the TNC to the Radio, Delays in the Transceiver. The Local Area Network, How TNCs Communicate, Controlling the Display of Monitored Packets, Setting Your TNC to Display or LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 10 Page 162 Ignore Packets, The Wireless LAN, Use of Packet Beacons, The Alert Call, The Target Call, LAN Answering Machine, Mail Beacon (Annunciator), Remote Beacon Shutdown. Connecting to Someone, Connecting to Other Stations the LAN-LINK Way, The Point and Shoot (MH List) Way, Using the Call Menu, Loop Backs, Names, Handles and Paths, Connecting via NET/ROM and TheNet, Connecting via KA-Nodes, The SAREX Call and Working MIR. Extending the Range, Digipeating, Using NET/ROM and TheNet Nodes, Using G8BPQ Nodes, Using KA-Nodes, Using MSYS Nodes, Using ROSE Switches, Using LAN-LINK to Communicate via Nodes, Path Determination to a DX Station, Finding Packet Signals, Using Communication Satellites. The Packet Bulletin Board System, How to Connect to the PBBS, Connected to the PBBS, Connected, But What Next ?, Telling it Your Name, Getting Information about the PBBS Itself, The Command Prompt Line, Changing the Prompt Line, Listing the Messages and Bulletins, Reading Messages, Sending Messages, Sending Messages Around the World, Sending a Bulletin, Forwarding Bulletins, Sending NTS Traffic, The Parts of the NTS Message, Killing Messages, Using LAN-LINK to Send NTS Traffic, Handling NTS Traffic, Files, Talk to the SYSOP, Connecting Elsewhere via the PBBS, Obtaining On-Line Help, Logging Off the PBBS, The F6FBB PBBS Features, Automating Message Reading, Message Headers. The PacketCluster, Summary of commands and features, Smartening Up PacketCluster Access With LAN-LINK. Other Applications of Packet, Data Base Servers, Using a REQFIL Server, Using a REQDIR Server, Using a REQQTH Server, Electronic Newspapers, Non Real-Time QSOs, Automatic Beacons, Robots and Contests, Propagation Research, Transmission Control Protocol/Internet Protocol (TCP/IP). This is a book to read once, then use as a reference over and over again. If you decide you don't like the book, send it back within 30 days for a swift refund. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 11 Page 163 Appendix 11 How Shareware Works The Association of Shareware Professionals (ASP) has established standards for its members and for any organization which has "ASP Approved" status. The ASP wants to make sure the shareware principle works for you. If you are unable to resolve a problem with an ASP member or organization (other than technical support), the ASP may be able to help. Please write to The ASP Ombudsman, 545 Grover Road, Muskegon, MI. 49442-9427, USA. You are encouraged to copy the floppy disk and share it freely with others. You have the luxury of trying out the product at your own pace and in the comfort of your own home or workplace. After you have used the material for a reasonable evaluation period (30 days), you should either discontinue use of the material or register your copy. Your support is important and greatly appreciated. With it, Shareware authors are encouraged to design and distribute new products. Without it, a great deal of high quality, low cost software will cease to be available. Why pay at all? You receive support from the author. You receive a CURRENT copy of the program. Your input and ideas help shape future products. You have a sense of pride and ownership in having honestly participated in the Shareware revolution. You help to keep software prices down by supporting a distribution method which doesn't depend on expensive advertising campaigns. Be aware of the following restrictions, designed to protect the community of Shareware users and to prevent greedy people from taking unfair advantage of the trust, hard work and good will of Shareware authors. 1. No price or consideration may be charged for the material. However, a distribution cost may be charged for the cost of the diskettes, shipping and handling, not to exceed $6. 2. The files and programs on the disks may not be modified or deleted. 3. The material cannot be sold as part of some other more inclusive package. 4. The material cannot be "rented" or "leased" to others. 5. The end user must be told clearly in writing on the outside of LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 11 Page 164 the package and in all advertising that the diskette(s) are "Shareware." 6. The package must contain a written explanation that the disk is for evaluation purposes, and that an additional "registration fee" is expected by the author, if the material is used beyond an initial evaluation period. 7. In the case of distribution via any telecommunications link, the following must be done: * An error checking protocol must be used. * The individual files must be combined into, and transferred in a library or archive format. 8. Shareware distribution is permitted only in the United States, Canada, England, and Australia. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Appendix 12 Page 165 Appendix 12 LAN-LINK 2.10 REGISTRATION FORM PLEASE COPY this form and MAIL to Joe Kasser G3ZCZ, P.O. BOX 3419, SILVER SPRING, MD 20918. CALL ________________ TODAY'S DATE ________________ NAME ______________________________________________ ADDRESS ___________________________________________ ___________________________________________________ CITY ______________________________________________ STATE _________ POSTCODE ____________ TNC TYPE_____ FIRMWARE REV ____ HOME BBS ______________ DISK SIZE 5.25 _____ 3.5 ____ Please register me as a user of LAN-LINK. I am currently using LAN-LINK Version ______ which I obtained from _______. Please send me the latest version of LAN-LINK or if a more recent one does not exist at this time, QSL my registration and add my name to the list to receive a free update when it becomes available. I also enclose an additional amount for evaluation copies of ELMER _, WHATS-UP _, PC-HAM _ and Startrek TCP _ ($5 for 1 program, $15.00 for the set). If I like them, I plan to register them in due course. Basic Packet Radio Book (29.95) __.__ Shipping for book $3.50 US/Canada, $6.00 overseas __.__ LAN-LINK Registration ($45.00) __.__ ELMER Registration ($45.00) __.__ Evaluation software __.__ ____________________________________ Maryland Residents please add 5% sales tax. __.__ Total Enclosed __.__ My favorite operating modes are ________________________. Additional Features I'd like to see in future releases of LAN- LINK. Keep Conference Bridge Up __ YAPP Binary File compatibility __ Expanded Contest Operation __ More AMTOR (explain below) __ NTS capability __ Picture Transfer capability __ Telephone Modem capability __ PacketCluster Menu (like BBS) __ Kenwood Radio Control Menu __ Dumb Terminal (CP-1, ST-5 etc.) __ Baudot/ASCII RTTY operation__ Many additions come into LAN-LINK as a result of user suggestions, so here's your chance to get some input in. Write them on this piece of paper. LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 166 INDEX AFSK, 72 Alarmwindow, 87, 142 Alt-A, 19, 57 Alt-B, 19, 64 Alt-C, 9, 19, 58, 97 Alt-D, 21, 42, 73, 93, 94, 103, 129 Alt-E, 19, 22, 57, 58 Alt-F, 22, 32, 116 Alt-H, 22, 57 Alt-J, 22 Alt-L, 22, 76 Alt-M, 15, 22, 74 Alt-N, 22, 96, 97 Alt-O, 23, 66, 76 Alt-P, 23 Alt-Q, 23, 35 Alt-R, 23 Alt-S, 23, 58, 75 Alt-U, 58 Alt-W, 23, 50, 125, 135 Alt-X, 8, 24, 58 Alt-Y, 12, 24, 135 Alt-Z, 24 AMTOR, 3, 4, 5, 6, 11, 14, 16, 17, 19, 20, 21, 22, 23, 26, 28, 30, 31, 32, 33, 37, 38, 45, 48, 52, 53, 69, 70, 72, 76, 79, 84, 88, 91, 92, 93, 99, 113, 116, 120, 125, 126, 129, 131, 135, 165 AMTOR-FEC, 16 Anomalies, 131 ANSI, 6, 12, 13, 48, 135 APLINK, 19, 84 ARQ, 19, 20, 21, 30, 91 ARSENE, 64 ASCII, 3, 4, 5, 6, 10, 15, 16, 20, 26, 27, 39, 47, 49, 50, 63, 64, 92, 102, 109, 114, 115, 116, 117, 120, 121, 124, 125, 129, 139, 148, 165 ASP, 163 Attempt, 15, 19, 21, 30, 37, 39, 45, 52, 66, 73, 77, 125, 129, 131 Audio, 6, 73, 75, 84, 160 Auto, 30, 34, 35, 38, 39, 90, 103, 104, 108, 111, 118 AUTO-Upload, 115 AUTOCQ, 14, 17, 91 AutoCR, 82 Autoexec, 150 Battery, 8, 9, 61, 62 BAUDOT, 3, 4, 6, 11, 16, 17, 20, 26, 27, 48, 60, 61, 63, 72, 91, LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 167 92, 93, 100, 108, 113, 116, 165 BBS, 1, 2, 5, 6, 7, 11, 20, 24, 25, 26, 39, 42, 44, 59, 62, 90, 106, 108, 111, 112, 115, 119, 121, 122, 129, 133, 135, 147, 148, 150, 151, 154, 155, 156, 165 BPQ, 162 BTEXT, 14, 73 Bulletin, 7, 16, 62, 78, 89, 107, 120, 162 Callsigns, 30, 56, 57, 58, 68, 69, 75, 79, 117, 126, 131 Capture-to-disk, 11, 16, 27, 28, 29, 40, 42, 43, 46, 47, 66, 69, 70, 77, 80, 89, 101, 102, 107, 111, 113, 130, 160 CFROM, 82, 104 Chirpcopy, 6, 32, 93, 94 Client-server, 14 Clock, 10, 34, 44, 45, 61, 69, 76, 85, 132, 161 Cluster, 6, 12, 24, 37, 84, 90, 108, 112 CMSG, 67, 68, 70, 83 COMMENTS, 53, 56, 57, 113, 115, 153 CONFIG, 106, 114, 157 CONOK, 68, 82, 104 Contest, 5, 6, 17, 23, 44, 45, 54, 55, 69, 75, 76, 110, 135, 159, 165 Control-C, 40 Control-F, 116 Control-Q, 133 Control-S, 133 Control-Z, 28, 52, 115, 119 Converse, 3, 24, 32, 50, 62, 71, 72, 74, 97, 98, 99, 121, 131 CQ, 5, 6, 14, 17, 18, 19, 22, 30, 31, 32, 34, 35, 38, 39, 64, 66, 69, 81, 91, 94, 95, 96, 99, 100, 101, 106, 107, 112, 126, 128, 129, 131 CQTEXT, 81 CR, 13, 91, 101 Ctdsk, 40, 42, 46, 47, 69, 111 CTEXT, 6, 60, 61, 62, 67, 68, 70, 106, 108, 118, 121, 135 CW, 10, 20, 27, 28, 71, 72, 84, 92, 93, 99, 100, 101, 102, 103, 108, 111, 112, 116, 130, 135 CWID, 99 Date-time-text, 28, 52, 127 Daytime, 161 DBASE, 5, 11, 53, 54, 56, 57, 113, 159 DCD, 69, 76, 97, 107, 129, 130, 132, 133 DCD-Flag, 132 DCDCONN, 97, 98 Digipeat, 5, 6, 18, 23, 66, 69, 71, 79, 95, 113, 121, 129 Digipeater, 74, 79, 82, 104 Directory, 5, 14, 21, 37, 38, 41, 43, 46, 48, 59, 74, 80, 107, 109, 113, 121, 141, 148, 150, 151 Disconnect, 4, 6, 14, 18, 20, 21, 22, 26, 29, 31, 32, 62, 69, 73, LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 168 74, 77, 78, 81, 90, 91, 92, 98, 111, 120, 132, 135 Download, 5, 11, 14, 24, 25, 26, 36, 37, 50, 52, 80, 81, 99, 107, 115, 120, 121, 123, 124, 127, 147 Dropouts, 111 DSZ, 146, 156 DUPLEX, 3, 4 Duplicates, 75 Echo, 28, 31, 69, 72, 73, 87, 113, 129 Echo-As-Sent, 129 Editor, 5, 10, 13, 15, 29, 39, 40, 41, 46, 60, 67, 98, 108, 114, 124, 139, 140, 144 ELMER, 5, 18, 34, 104, 105, 106, 107, 108, 109, 118, 135, 136, 137, 139, 140, 141, 142, 143, 144, 145, 161, 165 EOF, 28, 42, 52, 115, 116, 119, 126 Event, 5, 22, 25, 31, 34, 44, 45, 53, 62, 65, 70, 77, 79, 99, 120, 124, 127, 135, 154 Expand, 107, 110 FEC, 6, 20, 21, 23, 30, 32, 38, 99, 131 Flashing, 16, 17, 18, 27, 38, 39, 66, 70, 75, 89 FSK, 27, 72 Fuji-OSCAR, 160 Garbage, 111, 133 Gateway, 126 Greek, 8, 85, 133 Header, 5, 25, 38, 60, 65, 77, 87, 98, 120, 125, 128, 129, 157, 158 HEADERLN, 113 Huffman, 104 Incoming, 5, 6, 9, 15, 16, 25, 26, 27, 28, 31, 32, 37, 40, 42, 44, 47, 59, 61, 62, 66, 68, 71, 73, 85, 86, 87, 88, 90, 91, 97, 101, 102, 103, 109, 111, 113, 117, 118, 129, 131, 133, 136, 143, 144 IRQ, 85, 107, 109, 151, 152, 156 KA-Node, 5, 21, 113, 114 KAM, 3, 4, 9, 28, 31, 63, 71, 72, 76, 79, 83, 85, 91, 92, 93, 94, 96, 100, 102, 103, 104, 109, 111, 113, 129, 131, 133, 135 KM, 90, 112 KN, 26, 76 KPC, 3, 61, 128 LF, 13, 91, 101 LFADD, 72 LM, 24, 112, 115, 116 Log-to-disk, 69 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 169 Mail-Snatch, 25, 78, 129 MARS, 6, 17, 91, 100, 101, 135 MBX, 9, 51, 104, 106, 114, 115, 126 MCON, 95, 135 Metabeacon, 67, 68, 69, 98, 99, 135 MFILTER, 133, 134 MFJ, 3, 9, 31, 60, 63, 71, 72, 79, 85, 91, 92, 93, 111, 128, 129, 135 MH, 30, 50, 69, 86, 121, 125, 128, 129, 135, 162 MHwindow, 30, 86 MIR, 6, 64, 65, 66, 162 MRPT, 38 Multi-connect, 5, 32, 62, 96, 133 Multi-mode, 3, 7, 111 Multi-stream, 23 Multi-user, 25, 39, 96 MYCALL, 99, 102, 103 NAVTEX, 16, 92, 94, 135 NET, 5, 21, 113, 114, 116, 133, 162 NNNN, 91, 101, 102 Node, 3, 9, 24, 69, 72, 73, 107, 112 NTS, 39, 162, 165 Outwindow, 46, 86, 131, 141 Overseas, 165 PacketCluster, 6, 7, 11, 12, 17, 20, 24, 80, 84, 107, 108, 110, 112, 135, 162, 165 Pactor, 4, 6, 11, 12, 26, 48, 53, 91, 92, 93, 94, 103, 104, 116, 130, 135 Pcz, 117, 123, 124, 134, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157 PCZDIR, 151 PCZPORT, 147, 151, 152 PCZSPEED, 147, 151 PgDn, 40, 43, 57, 58, 59 PgUp, 27, 40, 57, 58 Printer, 16, 20, 23, 56, 69, 73, 108, 111, 135, 148 PromptWindow, 86, 141 QBM, 49, 50, 80, 107, 120, 121, 124, 125 QBU, 49, 81, 107, 116, 124, 127, 135 QBU-RX, 49, 81, 106, 107, 116, 124 QBU-TX, 49, 81, 106, 107, 116, 124 QDB, 49, 50, 90, 121, 125 QIC, 49, 50, 108, 112, 127, 135 QJG, 51, 126 QMH, 5, 49, 50, 121, 122, 125, 128, 135 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 170 QNO, 50, 51, 52, 75, 90, 120, 125, 126 QQQ, 91 QRA, 20, 23, 24, 50, 125 QRM, 3, 31, 65, 70, 125 QRT, 17, 50, 52, 65, 70, 82, 104, 125, 126, 127 QRU, 49, 51, 91, 114, 125, 126 QRV, 49, 51, 90, 119, 126 QRX, 50, 127 QRZ, 20, 23, 35, 67, 69 QSL, 50, 52, 53, 57, 65, 67, 69, 90, 120, 126, 165 QSL'd, 12, 84 QSM, 15, 49, 51, 117, 125 QSO, 4, 5, 14, 17, 19, 22, 23, 29, 32, 45, 48, 68, 70, 75, 76, 91, 93, 94, 95, 99, 101, 105, 106, 118, 131, 135, 136, 141, 143, 144, 145, 161 QSP, 17, 49, 51, 52, 69, 75, 106, 115, 119, 125, 126 QSY, 65, 70 QTA, 49, 52, 106, 117, 120, 126, 135 QTC, 5, 14, 15, 17, 69, 70, 73, 74, 78, 90, 107, 126 QTC-Snatch, 15, 74, 129 QTR, 49, 52, 127, 135 QZD, 49, 52, 117, 123, 124, 127, 135 QZD-RX, 117, 124 QZD-TX, 117, 124 QZU, 49, 52, 117, 123, 124, 127, 135 QZU-RX, 117, 124 QZU-TX, 117, 124 Random, 26, 113 REQDIR, 162 REQFIL, 162 REQQTH, 162 Retry, 20, 22, 23, 64 Reverse, 12, 27, 63, 125, 152 Robot, 14, 17, 19, 20, 23, 44, 45, 66, 67, 68, 69, 70, 99, 100, 159 Robot-Mailbox, 31 RTTY, 6, 17, 24, 26, 28, 31, 63, 71, 92, 93, 101, 129, 135, 165 RXR, 63, 64 RY, 24, 149, 155, 158 SARA, 63, 64 SAREX, 6, 17, 63, 64, 65, 66, 67, 68, 69, 89, 107, 135, 162 Scrollback, 27, 86, 135 SELCAL, 6, 7, 17, 19, 20, 21, 22, 23, 32, 37, 38, 79, 91, 100, 101, 102, 106 SOLO, 18, 72, 83, 95, 112 SSID, 79, 117 State-sequence, 90 StatusWindow, 86 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993 Index Page 171 Target, 5, 17, 18, 37, 38, 39, 70, 162 TheNet, 113, 162 Timeout, 81, 107, 109, 135 Transparent, 19, 32, 49, 50, 64, 135 TXR, 63, 64 Unproto, 66, 68, 96 Unshift, 17, 64, 101 Upgrade, 11 Verbose, 78 XFLOW, 11, 133 XMIT, 103 XMITOK, 10, 71, 72, 93, 135 Xmodem, 36, 122, 123, 146, 149, 154, 157, 158 XOFF, 152 XON, 152 YAPP, 114, 122, 165 Ymodem, 36, 37, 123, 146, 147, 149, 154, 157, 158 Zap, 6, 16, 17, 20, 24, 25, 26, 38, 39, 42, 44, 45, 62, 64, 65, 66, 69, 77, 78, 79, 89, 91, 92, 133 Zmodem, 6, 52, 117, 118, 123, 124, 127, 134, 135, 146, 147, 148, 149, 150, 152, 154, 156, 157, 158 LAN-LINK.DOC (c) G3ZCZ 1988 - 1993